Every “what is the status of my…” call is a portal that does not exist yet.
Customers call to ask when the next service is, whether the invoice was paid, and where the warranty document went. Staff answer from three systems. A portal is the same answer, available at 11pm, without anyone picking up.
Customer Portals & Admin Dashboards
Customer login with magic links or SSO, no passwords to reset.
Job history, next service date, invoices, receipts and card on file.
Documents that are actually findable: contracts, warranties, reports.
Self-serve reschedule and cancel that respects your rules.
An admin dashboard for your team with the same data from the other side.
Hooked into the tools you already run, so nothing is entered twice.
Platforms we use here
AWS
Postgres
Stripe
Jobber
40 / week
status calls one pest-control client stopped taking after launch
What you get
Customer portal
Admin dashboard
Integrations to your job and billing tools
Analytics on what customers actually use
From $9,500
Portal and admin together. Add-on integrations priced per connector.
Every price sits on the pricing page. Real numbers, no gate.
Discovery week
Five days inside your business before we write a line of code or put a number on a proposal. We shadow the actual work, not the org chart, because what owners say is broken and what is actually broken rarely match.
Day 1
The map
Read-only access to every system, and a list of who logs into what. By the end of the day the current process is drawn on one page, including the parts that live in someone’s head.
Day 2
Shadow the work
A morning beside the person who really runs it. We watch the spreadsheet, the phone, the retyping, and count the hand-offs where a job goes quiet.
Day 3
The paper trail
The last twenty quotes and invoices, a day of real calls and emails, the support inbox. The paperwork shows what happens; the interviews show what people think happens.
Day 4
Try the shelf first
An afternoon configuring the off-the-shelf tool that gets closest. If it does 80% of the job, that goes in the plan instead of a build, even though the build is the bigger invoice.
Day 5
The one-page plan
What to do first, what can wait, a fixed price per phase and a date for the first working slice. We read it together in thirty minutes.
What we look at
Every system you run, and who has the login
The spreadsheet everyone actually works from
Your last twenty quotes and your last twenty invoices
A day of real calls, emails and texts
Every hand-off where somebody retypes something
What an existing tool could do instead of a build
What you get
A one-page plan with a number on it
The sequence: what we build first, and why that piece
A fixed price per phase, with a place to stop between phases
The date the first working slice goes live
What we would configure instead of build
What you own at the end of it, and where it lives
The plan is yours to keep, whether we build it or someone else does.
Small, well-defined jobs do not need a week. A single API, a data migration or a one-screen internal tool gets the first call and a written quote, and we skip the shadowing.
Almost every plan changes after this week.