Who Does What: Roles on Your Team and Ours
Clear roles prevent dropped work. Here's who owns what on both sides.
Dropped work almost always traces back to unclear ownership, everyone assumed someone else had it. So we're explicit about who does what, on both sides, from the start. Here's the general shape; we'll tailor the specifics to your engagement at kickoff.
On our side
- Your lead. Your main point of contact and the person accountable for the engagement overall. When you're not sure who to ask, ask them.
- The build team. The people doing the hands-on work, configuring HubSpot, shaping data, wiring up processes and automations.
- Specialists as needed. Depending on your project, we bring in the right expertise for specific areas, so the person doing each piece of work actually specializes in it.
On your side
- The decision-maker. One person who can set direction and make calls. This is the single most important role you fill, because a build with no one to decide stalls fast.
- The process owners. The people who actually run the workflows we're touching. They're the source of truth on how things really work and the ones whose buy-in makes adoption stick.
- The access owner(s). Whoever controls your HubSpot, domains, and data, so we can get set up without chasing permissions.
Why we name roles up front
When roles are clear, questions go to the right person and get answered fast, decisions don't languish, and nothing falls between the cracks. When they're fuzzy, the opposite happens, and the project pays for it in delays. Ten minutes of clarity at kickoff saves weeks of confusion later.
Roles can flex
One person can wear several of these hats, especially in a smaller company, and that's fine. What matters isn't the number of people, it's that every responsibility has a clear owner. If a role is unassigned or unclear as the project goes on, we'll flag it, because an unowned responsibility is a problem waiting to happen.