HubSpot

On HubSpot suits a site whose main job is feeding the CRM: forms, personalisation and analytics connect without integration work, and marketers edit pages without a release cycle. Beside it, on a stack such as Next.js, suits a site with heavy design ambition, complex interactivity, or a development team that already ships web applications.

The CRM does not force the choice, because forms and tracking embed in an external site. The decision rests on who edits the site and how much engineering it warrants.

One-way, with the system of record outside HubSpot and the CRM receiving a read-optimised copy, is the simpler design and covers most sales and service needs. Two-way sync is a distributed-systems problem in miniature: each field needs one owning system, explicit conflict rules, and webhook handling that tolerates duplicate and out-of-order deliveries.

We build two-way sync where the process demands it, such as teams editing in both systems, and default to one-way everywhere else.

The integration side is. HubSpot's REST APIs are publicly documented with official client libraries, and the middleware around them is Node.js, so coding agents work in the densest part of the public corpus. The platform-specific side is thinner: HubL templates and workflow configuration have little public code to learn from, so that work stays human-led with agents assisting at the edges.

Integration code also offers a fast correctness signal, because contract tests against recorded API responses tell an agent immediately whether its change holds.

Either as a fixed cost for an initial outcome, such as a first release or a defined migration, or as a monthly rate for the team once later phases are under way. We do not publish a figure for a build, because the scale is set by the number of features, platforms, user groups and users, and projects have run from four weeks to several months. The How We Charge page sets out both models, milestone billing and the notice period.

Typically one full-time engineer on the build, with two part-time roles alongside: one running the project and one working with you on priorities and technical decisions. Teams are shaped around the system rather than around one technology, so HubSpot work draws in the neighbouring stack when it needs to. Delivery starts under Australian leadership, with the engineering in our Manila delivery centre.

Discovery establishes the scope, systems involved and delivery requirements. We agree the implementation plan and timing after that work, before implementation begins.