Glossary
Integration baseline
Initial dataset Kewbed pulls from existing PM tools to seed projects, people and allocations.
The integration baseline is the snapshot Kewbed takes from the tools a customer already uses to plan work. That usually means Excel rosters, Smartsheet schedules or MS Project files, exported once and mapped onto Kewbed's projects, people and allocations. The baseline is what populates the tenant on day one so the executive horizon and capacity matrix have something to display before any live sync is configured. It also means a studio does not have to migrate off its existing tools to evaluate the platform.
After the baseline lands, ongoing integration runs can keep the dataset in step with the source of truth without forcing the customer to abandon their existing workflow. That separation between the initial seed and the recurring sync is deliberate: it lets a studio start using Kewbed for executive reporting in days rather than waiting on a full tooling migration. It also keeps Kewbed honest about the data it is reading, since the baseline is a literal copy of what the producers and PMs already maintain.
Related: allocation, resource hierarchy, tenant organization. Compare with Productive, which expects teams to live in its own platform rather than reading from existing tools.
Last updated: 2026-05-13