Mobile Apps.
A logged-in surface your buyers and agents both use.
A customer portal is no longer just for support tickets. It is the buyer's first interactive surface — the place they (and the agents working on their behalf) query for status, configurations, contracts, and history. We build them as live context, not brochureware.
Mobile Apps is a Layer 01 service.
Every service we offer maps to one of four layers. Mobile Apps sits in the Surface — the layer that owns websites & customer portals.
A portal that holds context.
The old customer portal was a place to check ticket status. The V3 portal is a place where the buyer and the buyer's agent both query the company directly: pricing tier, integration status, usage data, contract terms, support history. It has the same answers as the rest of the surface, but personalized.
We build portals that share the same kernel as the public site. One source of truth. One MCP. The portal isn't a separate app with separate data — it's the same intelligence, with the lock removed.
The process.
Discover · use cases + entity model
Map what each buyer segment needs to query. Define which entities (account, user, deal, asset, ticket) the portal exposes.
Expose · API + auth
Stand up the read API on top of HubSpot (or your existing data layer). Wire authentication. Test that an agent on the user's behalf can resolve the same answers.
Wire · UI + flows
Build the portal UI against the design system. Conversational patterns where they fit, traditional dashboards where they don't. Every screen tested for both human and agent reads.
Operate · launch + adoption
Phased launch. Adoption tracking. Customer support trained on the portal as the source of truth, not a side surface.
A surface that compounds.
Things people ask before booking.
Is this a custom build or a SaaS portal product?
Custom — but on top of platforms you already pay for. We do not sell a portal product. We build it on top of HubSpot, your auth, your existing API. You own it.
How does this connect to our HubSpot data?
HubSpot is the kernel. The portal reads from it via authenticated API calls. Lifecycle changes, deal updates, ticket activity — all live, no copy-paste.
What does success look like at 90 days?
For Surface work: priority pages passing CLEAR, citation tracking live from week one, and the first measurable movement in how often AI engines cite you — typically between day 30 and day 90, because indexing runs slow at the start. The site keeps converting the humans it always did; now the agents deciding whether to send them can read it too.
Do we need to be on HubSpot for this to work?
Strongly preferred. The whole point is that lifecycle data, automation, and reporting all live in one source. We have adapted the model to Salesforce + Pardot and to HubSpot + custom data layers, but timelines double and the kernel is harder to keep clean over time.
See how mobile apps fits into The Surface.
The diagnostic starts where your buyers do: we walk your live site the way an AI engine reads it, then spend 90 minutes showing you exactly where the surface layer leaks. No slides — just your pages on the screen and a fix list in priority order.