A Knowledgable Team that Delivers Best In Class Results!
We hired Impulse Creative to build an entirely custom knowledge base and fully customizable landing pages on our HubSpot account. The team was super hands-on and responsive throughout the entire process, and their designer perfectly matched our new website's look and feel. At every step of the process, the Impulse team clearly communicated what we could expect and delivered on all of their promises without a hitch. It was an absolute pleasure working with this team and we look forward to more projects with them in the future!
LAYER 01 · THE SURFACE · CUSTOMER PORTALS
Customer Portals.
A portal that knows the customer.
FIG. 01 · OVERVIEW
Email threads, support tickets, and a forgotten login screen are not a portal — they are fragmentation. We build the live context layer between you and your customers: real-time data, agent-mediated support, self-serve workflows on top of one kernel.
FIG. 02 · WHERE IT LIVES
Customer Portals is a Layer 01 service.
Every service we offer maps to one of four layers. Customer Portals sits in the Surface — the layer that owns Websites & customer portals.
LAYER 01
Customer Portals LIVES HERE
The Surface
Websites & customer portals
Public interface — read by humans, agents, AEO crawlers.
→
LAYER 02
The Voice
Brand & omni-channel
Story rendered consistently in every format an LLM might cite.
→
LAYER 03
The Kernel
RevOps & HubSpot admin
Source of truth every agent calls first. Clean, opinionated, agent-ready.
→
LAYER 04
The Agents
AI consulting & co-pilots
Autonomous teammates running on the kernel.
→
A portal that holds context.
The 2018 customer portal was a place to check ticket status. The V3 portal is a live surface where the buyer and the buyer's agent both query the company directly: pricing tier, integration status, usage data, contract terms, support history.
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 for the right user. The ExtendStack KPI Dashboard is one worked example: every customer sees the metrics that matter to them, refreshed against HubSpot in real time.
The process.
PHASE01
Discover · use cases + entity model
Map what each buyer segment needs to query. Define which entities (account, user, deal, asset, ticket) the portal exposes — and which it deliberately does not.
PHASE02
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.
PHASE03
Wire · UI + flows + governance
Build the portal UI against the design system. Conversational patterns where they fit, traditional dashboards where they don't. Permission scopes so customers see only what they should.
PHASE04
Operate · launch + adoption + iteration
Phased launch. Adoption tracking. Customer support trained on the portal as the source of truth. Quarterly review feeds the next iteration.
A surface that compounds.
OUT 01
A live customer portal
A logged-in surface running on live kernel data — no brochure pages.
OUT 02
A read API on the kernel
Portal queries the same kernel the rest of your surface uses. One source of truth.
OUT 03
Agent-ready endpoints
External agents can query on the user's behalf, with auth and scoped permissions.
OUT 04
A measured adoption curve
Usage tracked from day one. Most-adopted features inform the next quarter's portal roadmap.
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 don't 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.
FIG. 06 · WHAT CLIENTS SAY
Why teams pick us for Customer Portals.
LAYER 01 · DIAGNOSTIC
See how Customer Portals 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.
90-minute call · L1 → L3 in 90 days or your money back