A new site design
Your whole HubSpot site rebuilt around your brand, with page layouts and settings your team can adjust themselves. Built to be added to over time rather than replaced again in two years.
The bigger jobs: a new site design, moving to HubSpot, fixing the automation, sorting the reports. Quoted from a written scope so you know the number before anyone starts.
Most project overruns aren't really a delivery problem at all, they're a scoping problem that didn't surface until eight weeks in.
So before there's any quote at all you get a written scope covering what's being built and what it will and won't do, along with what I need from you and by when, and what happens if any of that slips. If we can't agree the scope then we probably shouldn't be agreeing the project either.
The quote is then fixed against that document, and anything you want changing mid-build gets re-quoted and agreed before the work starts rather than discovered on the final invoice.
I take two projects at once and no more, which is the only reason the dates I give you mean anything. If I can't hit yours then I'll say so in the first conversation, and you'll have lost nothing but half an hour of your afternoon.
These are indicative starting points for a fairly typical scope, and yours would get quoted properly rather than picked off this list.
Your whole HubSpot site rebuilt around your brand, with page layouts and settings your team can adjust themselves. Built to be added to over time rather than replaced again in two years.
Sixty page layouts down to the eight you actually use, the rest safely archived, and the survivors labelled so anyone can tell them apart. The cheapest job on this list and often the biggest relief.
Bringing a site over from WordPress or anywhere else: pages, links, forms and tracking. The link mapping done carefully, because that's where these go wrong and sites disappear from Google.
Enquiries going to the right person, follow-ups that happen on their own, and your data staying tidy. Built so sales hear about a lead in minutes rather than at next week's meeting.
Dashboards for marketing, sales and the board that all agree with each other. Includes fixing what's being counted underneath, because that's usually the real problem rather than the charts.
A new HubSpot account set up properly on day one: how your data is organised, who can see what, what connects to what, and reporting that works from the start. Far cheaper than fixing it in year three.
Nothing moves on to the next phase until you've approved the one before it, which looks slower written down and turns out considerably faster in practice.
I go through your account, the existing site and whatever notes survive. You get an honest read on the state of things.
The written scope, the fixed price and the delivery date. You approve it before anything is built.
Work happens on private pages your customers can't see. A short written update every week, so you never have to ask where things are.
You and your team try it out on private preview links before anything goes live. Two rounds of changes are included.
Go live, then documentation and a walkthrough with whoever has to run it. 30 days of fixes after launch.
The price is fixed against the scope document, so if you want something added or changed part-way through then I write a short change note setting out the extra cost and what it does to the date, and you approve that before I touch anything. If there's no change note then there's no extra charge, which also means there's no quiet scope creep in the other direction.
Yes, and it often works rather well, with them holding the brand and the design while I hold the HubSpot side of things. The one thing I'd ask for is clear boundaries written into the scope, so that we're not both editing the same file in the same week and undoing each other's work.
That's a fair question to ask a one-person business and I'd rather answer it properly. Everything gets built inside your own account and written down as it goes, so somebody else could pick it up without starting again, and if a date is at risk I'll tell you as soon as I know rather than on the day it's due. Keeping capacity at two concurrent projects is partly about this, because it means one problem doesn't cascade into everything else.
Thirty days of fixes come as part of it, and after that you can book a consultancy session whenever you need one. There's no support contract attached, and the write-up is done properly enough that your team shouldn't really need one.
Say so on the first call and we'll scope the smaller version. Clearing out old layouts without the redesign, or sorting the reports without the data tidy-up underneath them, are both perfectly reasonable, as long as we're clear with each other about what the smaller job isn't going to fix.
Half an hour looking at your site and talking about your deadline is enough for me to tell you whether this is a project, a couple of sections, or something you'd be better off just doing yourselves.
Free scope call · Written quote in 2 working days