Updated June 25, 2026 by Sunny Chauhan.

The question I get most often from founders thinking about HubSpot Marketplace: "How long does it actually take to build a real app, end to end?" The honest answer is 8 weeks for a focused builder shipping a v1, 12 weeks if you're learning the stack as you go, longer if scope creeps. Most teams don't underestimate the build; they underestimate everything around it: the project setup, the scope discipline, the certification prep, the demo video. This guide is the full sequence: from "we decided to build a HubSpot app" to "the listing is live in the Marketplace." Architecture, tooling, the OAuth and webhook patterns, UI Extensions, certification path, and the 8-week timeline broken down week by week.

Pro Tip

TL;DR Building a HubSpot Marketplace app in 2026 takes 8-12 weeks for one engineer. The stack: HubSpot Developer Account + Projects CLI, OAuth public app, CRM API for data, webhooks for change detection, UI Extensions for in-HubSpot UI. The 8-week sequence: weeks 1-2 OAuth + app skeleton, weeks 3-4 CRM API integration, weeks 5-6 webhooks + UI Extensions, week 7 certification prep (demo video, scope audit), week 8 submission. Then 2-4 weeks Salesforce-side, sorry, HubSpot-side review queue. Costs are mostly engineering time. No HubSpot fees.

In HubSpot terminology, an "app" is a public OAuth app created in your Developer Account that customers install into their HubSpot portals. The app authenticates via OAuth, talks to HubSpot's APIs on the customer's behalf, can render UI inside HubSpot via UI Extensions, and (if certified) appears in the HubSpot App Marketplace.

What lives inside a typical app:

→ OAuth public app config in your Developer Account (Consumer Key, redirect URIs, scopes) → A server-side backend that handles OAuth callbacks, stores tokens, calls HubSpot APIs → Webhook subscriptions for relevant CRM object changes → UI Extensions for in-HubSpot surfaces (App Cards, workflow actions, Home Page widgets) → A Marketplace listing with metadata, screenshots, demo video

Most of these pieces are independent; you can develop them in parallel once the OAuth flow is working.

Free, sign up at developers.hubspot.com. The Developer Account is your workspace for creating apps and managing Marketplace listings. Separate from any customer HubSpot account.

For UI Extensions and the broader developer-projects framework:

``bash npm install -g @hubspot/cli hs init hs auth hs project create ``

This scaffolds a project structure with app.json, hsproject.json, and folders for extensions and serverless functions.

Pick whatever you know. HubSpot doesn't care. Node.js, Python, Go, Ruby all work. The OAuth flow and API calls are vanilla HTTP. The backend stores tokens, handles webhooks, and orchestrates the integration logic.

Tokens, customer mappings, sync state. Postgres is the boring right answer for most ISVs. Redis on top for rate-limit state and locks.

Spin up at least three HubSpot sandboxes from your Developer Account for development, QA, and demo. See our HubSpot sandbox setup guide.

→ Create the Developer Account → Create your first app inside it (Consumer Key, Consumer Secret, redirect URI) → Pick initial scopes (minimum viable, see our OAuth scopes guide) → Build the OAuth redirect handler in your backend → Implement code-for-token exchange → Implement token storage (encrypted at rest)

End of week 1: you can install your app into a sandbox via OAuth and you have an access token stored on your server. That's the foundation.

→ Implement refresh-before-expiry logic → Handle rotated refresh tokens correctly → Implement the uninstall webhook (delete tokens on customer uninstall) → Add CSRF protection via state parameter → Move client secret to a secrets manager

End of week 2: OAuth is production-quality. Customer installs, your app holds valid tokens, customer uninstalls, your app deletes them cleanly.

→ Implement read operations for the CRM objects your app cares about → Implement cursor pagination correctly (after parameter, not offset) → Implement batch reads (100 records per call) → Cache the customer's property schema (12-24 hour TTL) → Discover custom properties at runtime (don't hardcode)

End of week 3: your app can query a customer's CRM data.

→ Implement single-record create and update → Implement batch writes (100 records per call) → Implement association management → Implement idempotency for writes (safe to repeat) → Add per-portal rate limiter (token bucket, 100/10s)

End of week 4: your app can read AND write CRM data, respecting rate limits.

→ Configure webhook subscriptions in your Developer Account → Implement webhook signature verification (X-HubSpot-Signature-v3) → Implement the ack-fast-process-async pattern (return 200 in under 5 seconds) → Make webhook handlers idempotent → Wire webhook events to your business logic

End of week 5: real-time change detection works. When a customer updates a CRM record, your app knows. See our HubSpot webhooks implementation guide.

→ Initialize a UI Extension project (hs project create) → Build an App Card for a CRM record (Contact, Deal, or Ticket) → Use HubSpot's @hubspot/ui-extensions primitives (not foreign design systems) → Add a serverless function for authenticated backend calls → Deploy via hs project upload

End of week 6: your app has a native UI surface inside HubSpot. This is a Marketplace differentiator. See our HubSpot App Cards and UI Extensions guide.

→ Audit your scope list (drop scopes not exercised in last 30 days) → Build out the listing copy (treat as landing page, not doc dump) → Record a demo video showing core flows (replaces the old test-credentials requirement as of March 2026) → Set up monitoring (429 rate, webhook success rate, sync errors) → Run end-to-end testing in two sandboxes → Get 3+ installs (sandboxes count, beta customers count, mix is fine) → Live privacy policy, terms, setup page URLs

End of week 7: certification submission package is ready.

→ Submit listing for review → Wait 2-4 weeks for HubSpot's Ecosystem Quality team → Address review feedback (common: unused scopes, demo video gaps, missing security questionnaire answers) → Resubmit if needed (one round of feedback is typical)

End of week 8 + 2-4 review weeks: app is live in the HubSpot Marketplace.

The 8-week schedule assumes scope discipline. The common scope-creep patterns that extend it to 16+ weeks:

→ "While we're at it, let's add support for custom objects." Adds 2-3 weeks for runtime schema discovery, custom property handling, association edge cases.

→ "Let's also build a workflow action." Adds 1-2 weeks for the workflow action UI Extension surface, configuration model, and execution path.

→ "Marketing wants the listing copy to be more 'brand'-y." Adds time but not necessarily eng time; just blocks shipping.

→ "Let's wait until we have 5 beta customers to submit." Adds however long it takes you to land 5 betas. Sometimes weeks, sometimes months.

The discipline that works: ship a focused v1, then add scope post-launch. Marketplace listings can update without re-review for most changes.

Cost categories for an 8-week build with one mid-senior engineer:

The big number is engineering opportunity cost, not cash. HubSpot itself charges nothing. Compare to a Salesforce AppExchange app: $999 security review submission fee, 15% revenue share, plus same engineering time. HubSpot's cost structure is materially friendlier for ISVs.

At Appnigma we generate Salesforce 2GP Managed Packages from natural-language prompts, compressing what's normally a 6-month custom build into days. The HubSpot equivalent (generating a complete OAuth-aware HubSpot app with CRM integration, webhooks, UI Extensions) would compress the 8-week build to a similar order of magnitude.

This isn't shipped for HubSpot yet but the patterns are documented enough to generate deterministically. The future where founders prompt for "a HubSpot Marketplace app that syncs meeting summaries to deal records" and get production-ready scaffolding is real. Until then, manual building means following the 8-week sequence above.

• [ ] Decided what your app does in one sentence (scope discipline) → Yes / No

• [ ] Validated customer demand (talked to 5+ customers) → Yes / No

• [ ] One engineer allocated full-time for 8-12 weeks → Yes / No

• [ ] HubSpot Developer Account created → Yes / No

• [ ] Backend stack chosen (Node, Python, Go, etc.) → Yes / No

• [ ] Database for tokens decided → Yes / No

• [ ] At least three sandboxes spun up → Yes / No

• [ ] Initial scope list drafted (minimum viable) → Yes / No

• [ ] Privacy policy, terms, setup page URLs planned → Yes / No

• [ ] Demo video plan (script, recording approach) → Yes / No

A B2B billing product (analogous to Monk or Salesbricks on Salesforce) shipped their HubSpot Marketplace app v1 in 9 weeks following roughly the sequence above.

→ Weeks 1-2: OAuth flow, token storage in AWS Secrets Manager, uninstall handler → Weeks 3-4: CRM API integration for deals and contacts, batch endpoints, rate limiter → Week 5: Webhook handler for deal property changes → Week 6: App Card on the Deal record showing current invoice status → Week 7: Demo video, scope audit (dropped 3 unused scopes), monitoring setup → Week 8: Submission to certification → Week 9 + 3 weeks review queue: live in Marketplace

Total elapsed: 12 weeks from kickoff to live listing. Total cost: ~$45K in fully-loaded engineering time, ~$1K in infrastructure, ~$2K in demo video production. The annual savings vs Workato Embedded ($60K/yr in their cost model) paid for the build in year 1.

8-12 weeks for one mid-senior engineer shipping a focused v1. Add 2-4 weeks for HubSpot's certification review queue. Scope creep can extend this to 16+ weeks; the discipline that works is shipping a focused v1 and adding features post-launch (HubSpot Developers, listing requirements).

~$33K-$40K total for an 8-week build by one engineer: $31K in fully-loaded engineering time, $2K-$5K in infrastructure and demo video, $0 in HubSpot fees (no listing fee, no certification fee, no revenue share). Salesforce AppExchange equivalent: same eng cost + $999 review fee + 15% rev share ongoing.

HubSpot Developer Account, HubSpot CLI (@hubspot/cli), Developer Projects framework, your backend stack of choice (Node, Python, Go, etc.), a database for tokens and customer state, and at least three HubSpot sandboxes for development, QA, and demo.

No. HubSpot doesn't require a developer certification to build or list apps. Any engineer with API integration experience can build one. HubSpot does have certification programs for marketing and CRM admins, but those aren't required for ISV builders.

For most CRM-syncing apps: oauth, crm.objects.contacts.read, and one or two object scopes specific to your app's purpose. Three to five scopes total. Add scopes only when a real feature uses them; HubSpot's certification review flags scopes that haven't been exercised in the last 30 days. See our HubSpot OAuth scopes guide.

Limited in 2026. Connector platforms (Zapier, Make, Workato) let non-engineers configure middleware-style integrations, but those can't be listed on the Marketplace. For a real Marketplace app with OAuth, webhooks, and rate limiter, you need engineering. No-code platforms for HubSpot app generation are emerging but less mature than the Salesforce equivalent.

Submit your listing from your Developer Account. HubSpot's Ecosystem Quality team reviews. Timeline in 2026: 2-4 weeks. Common feedback: unused scopes, missing demo video, security questionnaire gaps, privacy policy URL issues. Most apps go through one round of feedback. See our HubSpot app certification requirements.

Optional but recommended for Marketplace differentiation. Most listed apps in 2026 still don't have UI Extensions. An App Card that renders inside HubSpot's CRM record sidebar makes your listing visually distinct and increases engagement. See our HubSpot App Cards and UI Extensions guide.

Sunny Chauhan is the founder and CEO of Appnigma AI, a no-code platform that generates Salesforce AppExchange-ready Managed Packages from natural-language prompts. He holds Salesforce certifications in Platform Developer II, Platform App Builder, Administrator, Data Cloud Consultant, and AI Associate. Appnigma has helped B2B SaaS companies including Warmly, Hyperbound, Pylon, Seam AI, and Avoma ship native Salesforce Managed Packages; the 8-week sequence above transfers the same architectural discipline to HubSpot Marketplace app builds.

Originally published June 25, 2026. Last reviewed June 25, 2026. Build sequence, timeline, and cost ranges based on Salesforce ISV build experience adapted to HubSpot specifications current as of the published date.

• HubSpot Marketplace Complete Guide

• HubSpot Custom Integration Build Guide

• HubSpot API Builder's Guide

• HubSpot OAuth and Scopes Complete Reference

• HubSpot Webhooks Implementation Guide

• HubSpot App Cards and UI Extensions

• HubSpot Sandbox Setup Guide

1/ HubSpot Developers, Listing Your App 2/ HubSpot Developers, OAuth Quickstart Guide 3/ HubSpot Developers, CRM API Reference 4/ HubSpot Marketplace Certification Requirements

What's the one-sentence description of your app, and which week of the 8-week sequence is the riskiest for your team?