What working with me looks like.

I diagnose, design and deliver operational systems spanning quoting, delivery, billing and customer operations in HubSpot and the systems around it. That might mean repairing an inherited integration, connecting a quoting workflow or building an interface for the person doing the work. I start with the task your team is struggling to complete.

Yes. I work directly with you to understand the problem, design the solution and lead delivery. I’m hands-on with the technical work, and I bring in the USS team where the project needs it. You’ll know who is building, who needs your input and who to contact.

Bring a recent example: a quote that took too long, a job waiting for an invoice or an integration that failed. I’ll ask how it works today, where it gets stuck and what a better result would look like. You don’t need to write a technical brief first.

Where scope, access and client availability support it, we commit to a first useful improvement within 30 days. That could be a quoting step, a repaired data flow or a card that brings needed information into HubSpot. Before we start, we agree the scope, access, decisions and tests needed to deliver it. Larger projects can build on that first result.

We agree the meeting and update schedule before starting. I show the work as it develops and flag decisions that need your input. Your team tests the change with real examples before we call it ready.

A defined project has a fixed fee. Ongoing support and improvement have an agreed monthly fee covering specific responsibilities. Your proposal explains what is included, what you need to provide and how changes will be handled. I quote the work before we begin.

No. Our usual starting point is a defined repair or build, with the review of relevant systems included in week one. We agree scope and acceptance before starting, then check the underlying behavior during delivery.

Yes. I can handle a technical part of a wider project, add delivery capacity or work directly with the person who runs your system. For partner work, we agree how I’m introduced, who speaks with the client and which parts each team owns.

Access to the relevant systems, someone who can make decisions, and the people who know the daily work. I’ll tell you which examples and reviews are needed so your team can plan its time.

We test the agreed cases, walk your team through the result and provide the documentation included in the proposal. We also agree who handles support and future changes. Ongoing work makes sense when there is an ongoing job for us to do; a handover may be all you need.