Planned connections, not live claims. Confirm capabilities, permissions and ownership.Outbound requests / messages require their own authorization.
One front door does not imply third-party single sign-on or provisioned access03 / 08
03 · Welcome to your dashboard
Start your day knowing what comes next.
Your Pulsia home brings your HRN progress, installer requirements, training and tools into one clear view.
PulsiaHomeRun Network · My dashboard
Your next step, right in front of you.
See what to finish, what you can use and who can help.
Preview of the planned experience
What should I do next?
Pick up where you left off.
Find your next onboarding step or lesson, with clear instructions and a person to ask for help.
My next stepAsk for help
How am I doing?
Joining HRNYour progress
Your installerWhat’s left to finish
Your trainingYour next lesson
Ready to work?Manager’s go-ahead
What can I use?
Your tools, in one place.
See which tools are ready, which need setup and how to get started. No guessing where to go.
FieldCoachInstaller tools
My appointmentsMy dealsMy trainingMy commissionsMy team
For reps: follow your progress from joining HRN to working with your assigned installer, without hunting through messages.
For managers: see who needs help, what they are waiting on and where a quick follow-up can keep them moving.
Your manager confirms when you are approved to work04 / 08
04 · Operating facts meet financial truth
Connect Revenue and Finance. Don’t duplicate them.
Revenue explains rep obligations. Finance owns the company’s books. Mercury provides bank facts to reconcile.
Revenue · untested build
Integrate, don’t rebuild.
Inventory John’s existing module, test its capabilities and agree the event contract.
Finance · existing foundation
Protect the company books.
Revalidate balanced entries, reversals, tenant isolation and accountant exports.
Mercury · planned connection
Visibility before money movement.
Verify supported API access. Start with read-only data and reconciliation.
Company finances: authorized owner / finance only · Reps: their permitted Revenue records05 / 08
05 · Help, right inside your dashboard
Ask Pulsia. Get back to your day.
Instead of chasing updates across messages and websites, ask a question about your work in plain language.
A look at the planned experience“What is holding up my installation, and what do I need to do?”As a manager: “Which deals on my team need attention today?”
01 / ASK
Get a clear answer.
See what has happened with your deal, when it was last checked and what needs attention.
02 / CHECK
Look for an update.
Ask Pulsia to check for newer information. If the installer has not provided it, you’ll know.
03 / FOLLOW UP
Have a message ready.
Ask for a follow-up to the installer, with your deal details and the question you need answered.
04 / REVIEW
You stay in control.
Review the message and who will receive it before you approve sending. Keep the reply with your deal.
For reps: spend less time chasing an answer and more time knowing what to do next.
For managers: spot the deals that need help and keep the right people informed.
If Pulsia doesn’t know, it tells you. No guessed dates or promises.You decide when a follow-up is sent.
Planned experience · Available updates depend on your installer06 / 08
06 · Recommended delivery map
Build a usable rep home. Start integrations early.
Progress in small accepted releases, with installer discovery and financial intake running in parallel.
People & daily workThe primary product path
1 · Close the entry releaseApplication-to-approval gates, branding and clear errors.
2 · Rep workspaceReal HRN content, one installer track, tools and next actions.
3 · Training pilotOne approved learning path, practice and human review.
Installer & deal flowStart discovery alongside the workspace
Select the first partnerAPI contact, access, real stage definitions and required fields.
Prove a read-only feedDeal matching, source freshness, retries and exception handling.
Add requested assistanceShared status views, answers and governed follow-up.
Revenue & company booksReuse existing builds
Intake & validateInspect Revenue and finance-v1; resolve overlaps and permissions.
Agree event contractsRep, company, deal and financial references with auditability.
Reconcile with MercuryAuthorized read-only bank facts matched to company records.
Across every lane: preserve Pulsia branding, mobile usability, data boundaries and human approvals. Continue existing Field work without silently enabling connectors. Dates follow partner access, content readiness and accepted scope.
Recommended sequence, not a promised schedule or blanket implementation authorization07 / 08
07 · Align before expanding
What we have. What we decide next.
A working test journey is a strong foundation. The next step is a small, real operating slice for HRN.
Current planning baseline
Area
Evidence level
Next gate
Onboarding flow
Synthetic test passed
Production gates, real content and branding fix.
Field / Coach
Existing foundations
Verify current fit, integration and approved content.
Pulsia Revenue
Built, not tested
Receive handoff, inspect and validate.
finance-v1
Earlier isolated tests
Revalidate current build and integrate.
Installer / Mercury
Connections planned
Confirm capability, access and source mapping.
Discussion with Erica
Which installer should we prove first?
Choose the partner, product, region and contact who can validate its requirements and deal feed.
What must a new rep finish before working?
Confirm HRN vs installer requirements, the content approver and the manager sign-off boundary.
What should be visible every day?
Prioritize the rep’s next action, manager exceptions and the most useful deal updates.
Our next useful release: one Pulsia-branded rep workspace, one approved HRN onboarding path and one installer requirements track, while the first API connection is prepared.
Planning snapshot · September 16, 2026 · No live provider or production claim08 / 08
Pulsia × HomeRun Network · Planning presentation for John & Erica. No customer, bank or credential data is included. This shareable link is not an authenticated workspace. Production access, financial actions and external communications require separate authorization.