Your first 30 days

Last updated: August 27, 2026

Every engagement is scoped differently, so treat this as the shape rather than a schedule. Your scope of work is the authoritative document; this is what the rhythm usually looks like.

Week 1: access and orientation

We ask for admin access to your HubSpot portal and whichever source systems are in scope. The list is always specific, never "everything", and if something on it makes you uncomfortable, say so and we will explain why we asked or work without it.

We also want to see how your team actually works today, including the spreadsheets and the workarounds. That is not a judgement exercise. Those workarounds usually mark exactly where the system failed people, which makes them the most useful thing you can show us.

Week 2: the findings conversation

We come back with what we found. Expect this to be direct. If the thing costing you revenue is not the thing you hired us to fix, we will say so then rather than six weeks in.

This is the point where scope sometimes changes. It is much cheaper to change it here than after the build starts.

Weeks 3 and 4: building

Work begins on whatever the findings prioritised. You will see things appear in your own portal as they are built, rather than getting a reveal at the end.

What makes this go faster

A decision-maker available for the architecture calls. Not every call, just the ones where we are choosing between approaches. A decision deferred a week usually costs more than the meeting would have.

One named point of contact on your side. Someone who can answer questions and chase internal approvals.

Honesty about constraints. Budget, politics, a system nobody is allowed to touch. Knowing about a constraint early means designing around it. Discovering it late means rebuilding.