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.
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.
What a HubSpot app actually is
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:
Most of these pieces are independent; you can develop them in parallel once the OAuth flow is working.
The toolchain
HubSpot Developer Account
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.
HubSpot CLI and Developer Projects
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.
Your backend stack
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.
A database
Tokens, customer mappings, sync state. Postgres is the boring right answer for most ISVs. Redis on top for rate-limit state and locks.
Sandboxes
Spin up at least three HubSpot sandboxes from your Developer Account for development, QA, and demo. See our HubSpot sandbox setup guide.
The 8-week build sequence
Week 1: Developer Account and OAuth skeleton
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.
Week 2: token refresh, OAuth hardening
state parameterEnd of week 2: OAuth is production-quality. Customer installs, your app holds valid tokens, customer uninstalls, your app deletes them cleanly.
Week 3: CRM API reads
after parameter, not offset)End of week 3: your app can query a customer's CRM data.
Week 4: CRM API writes
End of week 4: your app can read AND write CRM data, respecting rate limits.
Week 5: webhooks for change detection
X-HubSpot-Signature-v3)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.
Week 6: UI Extensions (optional but recommended)
hs project create)@hubspot/ui-extensions primitives (not foreign design systems)hs project uploadEnd 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.
Week 7: certification prep
End of week 7: certification submission package is ready.
Week 8: submit and respond to feedback
End of week 8 + 2-4 review weeks: app is live in the HubSpot Marketplace.
What scope creep does to the timeline
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 breakdown
Cost categories for an 8-week build with one mid-senior engineer:
| Item | Cost |
|---|---|
| Engineering time (8 weeks @ $200K fully-loaded annual) | ~$31K |
| HubSpot Developer Account | $0 |
| HubSpot Marketplace listing | $0 |
| HubSpot certification | $0 |
| Infrastructure (backend, DB, monitoring) | $200-$2000 first-month spend |
| Demo video production | $500-$5000 |
| Static IP for OAuth (if needed) | $50-$200/mo |
| Total cash + opportunity cost | ~$33K-$40K |
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.
How no-code generation changes the calculus
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.
Pre-flight checklist before starting a HubSpot app build
- [ ] 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
Real-world scenario: a billing ISV ships v1 in 9 weeks
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.
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.
Frequently Asked Questions
How long does it take to build a HubSpot Marketplace app?
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).
How much does it cost to build a HubSpot app?
~$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.
What's the toolchain for building a HubSpot app?
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.
Do I need a HubSpot certified developer to build a HubSpot app?
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.
What's the minimum viable scope list for a HubSpot app?
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.
Can I build a HubSpot app without code?
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.
What's the HubSpot Marketplace certification process?
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.
Do I need UI Extensions for my HubSpot app?
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.
About the author
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.
Related articles
- 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
Sources
- HubSpot Developers, Listing Your App
- HubSpot Developers, OAuth Quickstart Guide
- HubSpot Developers, CRM API Reference
- 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?
