Development for HubSpot® users

Customer data your
teams can trust

We set up, customize and connect HubSpot to your product and data, with records designed for how you sell and support, and access kept to what each app needs, so every team works from the same record.

Thanks, we’ll be in touch soon.

{{ heroStatus }}

You’re in good company

A few of the companies we’ve worked with.

When the record outgrows its fields

Many companies start HubSpot with contacts and a few properties, the fields each record keeps, then add a property for each new need, until a record carries far more fields than anyone reads, some filled in by hand and some by integrations no one remembers adding.

HubSpot matches contacts by email address, so when the same customer arrives through a form with one address and an import with another, the account keeps two records, and the two drift apart.

Integrations added one at a time call older API versions, or run as legacy private apps, which HubSpot has set an end of support for. So reports need explaining, and teams keep their own lists on the side.

What we build

HubSpot shaped around how you sell and support, and connected to the systems you run, with each change tried in a sandbox or a test account before it reaches your live account.

  • Records designed for how you sell and support

    Objects, properties, pipelines (the stages a deal or ticket moves through) and associations planned together, with custom objects where your Enterprise subscription includes them, so each record holds what its team needs.

  • Connections to your product, billing and support tools

    Records kept in step with the systems you run, through HubSpot’s current API versions and webhooks, with one system in charge of each field.

  • Moves into HubSpot

    Records and the links between them imported from spreadsheets or another CRM, with duplicates found and matched first, by email, company domain or record ID, as HubSpot’s import docs set out.

  • Apps inside HubSpot

    App cards on records, app pages and settings, built on HubSpot’s developer platform at its current version, so your team sees what it needs from your product without leaving the record.

  • Integrations moved to current versions

    Calls on the numbered API versions moved straight to the date-based ones, as HubSpot advises, and legacy private apps moved to service keys or project-based apps, as the section below explains.

  • Automation where workflows need code

    Custom code actions in workflows, which need a Data Hub Professional or Enterprise subscription, and webhooks for what the standard actions can’t do, each tested and documented.

  • Content Hub sites

    Themes and modules your marketing team can edit, built as HubSpot’s CMS docs set out, and site moves with every old address redirected to its new page, as Google’s guidance on site moves recommends.

  • Reports your teams can trust

    Each property defined once, with one meaning, and data checked where it enters, so a number means the same thing in every report.

  • Access kept to what each app needs

    Service keys and apps with only the scopes they need, user-level apps where each person should act as themselves, and keys rotated on a schedule. For AI assistants, HubSpot’s MCP server, with each person acting as themselves.

    MCP & Agent Integration

Records linked the way your business works

HubSpot keeps each kind of thing as its own record: contacts, the people; companies; deals; and tickets, the requests your support team works on. With an Enterprise subscription you can add custom objects, kinds of record you define yourself. Each record keeps its details in properties, the fields your teams fill in.

Records are linked by associations, and a link can carry a label that says what it means, such as the contact who decides on a deal. So a deal can show who decides and who pays, and segments, workflows and reports can follow those links, instead of piling more fields onto one record.

That model shapes what every team sees, automates and reports on, so we design it before anything is built on it.

{{ rcCenter.name }}{{ rcCenter.kind }}
    •

Each customer is kept once, and linked to everything that belongs with them.

{{ rcStatus }}

Integrations age on a schedule

HubSpot now releases a new version of its APIs and its developer platform every March and September. Each version is Current for its first six months, then Supported, with critical fixes, until it goes unsupported 18 months after its release.

Older integrations call the numbered APIs, v1 to v4, or run as legacy private or public apps, the kinds HubSpot built before its current developer platform. HubSpot has said that v1 to v3 and legacy apps go unsupported in September 2027, and that support for v4 ends on March 30, 2027. It’s also turning off the creation of new legacy private apps, and points new integrations inside an account to service keys, credentials that each carry only the scopes they’re given.

HubSpot supports them until then, so each integration can move in planned steps, straight to the date-based versions, as HubSpot advises. We check each one for the API versions it calls and the kind of app or key it runs as, and move it before its support ends.

Start with a review of your account

The review covers your objects, properties, pipelines and associations: which are used, which repeat and which reports rely on them; how records are matched, and where duplicates come from; each integration, what it reads and writes, the API versions it calls, the kind of app or key it runs as, the access it holds and where it stands on HubSpot’s dates; your workflows, and any custom code in them; your users, teams and permissions, and who can export data; your Content Hub site, if you have one; and how changes are tried before they reach the live account, in a sandbox on an Enterprise subscription or in a free developer test account.

Moving into HubSpot, or adding a new integration? We design the data model first, then build one connection, try it with real records and release it early, so your team works with it before the rest is built.

Either way, you get a written review and a proposal for the first step.

Questions worth asking

  1. Will HubSpot’s changes in 2027 affect our integrations?

    If they call the numbered APIs or run as legacy apps, yes. HubSpot has said that v1 to v3, legacy public apps and legacy private apps go unsupported in September 2027, with no more bug fixes, reliability improvements or security updates for them, and that support for v4 ends on March 30, 2027. Its developer home shows which of your apps call these APIs, and it plans to document the replacement for each legacy API in full in its March 2027 release. The review lists each integration, what it calls and the steps to move it.

  2. We use a legacy private app. What should we do?

    Keep it running while you plan the move: HubSpot says existing legacy private apps keep working as they are. An integration that only makes API requests can move to a service key, with only the scopes it needs, a log of its requests and a key you can rotate; one that needs webhooks, or works inside HubSpot, moves to a project-based app on HubSpot’s developer platform. From October 26, 2026, an existing account can’t create new legacy private apps.

  3. Can an app act with each person’s own permissions?

    Yes, with a user-level app on version 2026.09 of HubSpot’s developer platform. It acts on behalf of the person using it, within their own HubSpot permissions, instead of with account-wide access, and HubSpot’s audit logs show the person and the app. Some features, such as app cards, webhooks and serverless functions, still need account-wide access, and an existing app can’t be switched over, so the review says which fits each app.

  4. Can our AI assistants use our HubSpot data?

    Yes. HubSpot’s MCP server lets an AI assistant or agent read and update HubSpot records as the person using it would, through a user-level app, so it reaches only what that person may see, and its changes show in HubSpot’s audit logs under that person’s name. We set it up with the fewest scopes the work needs.

    MCP & Agent Integration

  5. Do we need a higher HubSpot plan for this?

    Sometimes. Some features need certain subscriptions: custom objects and sandboxes need an Enterprise subscription, and custom code in workflows needs Data Hub Professional or Enterprise. We say which features the work needs before anything is bought, and design for the subscription you have where we can.

  6. Should we build inside HubSpot, or in our own product?

    It depends on who uses it. What a team needs while working on a record can sit in an app card on that record; the rules your product runs on stay in your product, and HubSpot receives what its teams need. The review weighs each case.

  7. Can you move us into HubSpot from another CRM or from spreadsheets?

    Yes. We map your records to HubSpot’s objects and properties first, find and match the duplicates, then import the records and the links between them, trying the import on a sample before the full one.

  8. Can you build our website on Content Hub?

    Yes. We build themes and modules your marketing team can edit in HubSpot’s page editor, with HubSpot hosting the site, and move your existing pages with every old address redirected to its new one.

    Web & App Development

  9. Can you take over our existing HubSpot setup?

    Yes. We start by reading how the account is set up, from its objects and properties to its workflows and integrations, and note who has access, with which permissions. The review then says what to change and in what order, and nothing changes in the live account until you’ve agreed to it.

  10. Can it connect to our ERP, billing and support tools?

    Yes. Each connection starts by deciding which system is in charge of each field, then moves data through HubSpot’s current APIs and webhooks, and every connection is documented and watched.

    Systems & API Integration

  11. How do you keep our data secure?

    Each integration gets its own key or app with only the scopes it needs, and keys are rotated on a schedule, or at once if one is exposed; service keys keep a log of their requests. People get the permissions their work needs, and every change is tried before it reaches the live account. Our security work adds threat modeling, code review and checks in every build.

    Application Security

  12. What does it cost?

    It depends on the account: its records and integrations, and whether it’s being set up, moved or extended. You get a written proposal before any work starts: the scope, the price or rate, and how you pay.

    Pricing

  13. Can your developers work in our own team?

    Yes. Tell us what your account needs, and we’ll introduce developers who work with HubSpot, matched to it, within 48 hours, working in your time zone. You meet them and decide who joins.

HubSpot is a registered trademark of HubSpot, Inc. Webair is independent of HubSpot, Inc., and isn’t authorized by, endorsed by, sponsored by, affiliated with or otherwise approved by HubSpot, Inc.

Let’s build it better

Tell us how your records are set up and what connects to them today. A short call is enough to see where to start.

Thanks, we’ll be in touch soon.

{{ ctaStatus }}