Custom applications · 16 July 2026 · 8 min read
Clients expect a portal — not another PDF in email. Here is when to build custom, what it should do in phase one, and how to ship without a six-month agency death march.
Agencies, trades groups, and professional services firms in SEQ hit the same wall: clients want job status, documents, and approvals in one place — but the job system, SharePoint, and email each hold part of the story.
Off-the-shelf client portals force your process into their workflow. Custom portals do the opposite: enquiry → job → invoice mirrors how you actually deliver — with auth, notifications, and audit trail included.
Login for clients and internal staff. View job status and key documents. Approve quotes or variations. Download invoices. Email notifications on state changes.
Defer chat, AI summaries, and mobile apps until phase one is live and used. MVPs that ship beat portals that demo.
React or Next.js frontends with Supabase, GCP, or Azure backends are common for SMB portals. Row-level security so clients see only their jobs. HTTPS, secrets in vaults, audit log for downloads.
If you vibe-coded a prototype in Cursor, Ship (FC-10 Launch Safe) gets it production-grade before real client data lands.
Configure SharePoint or your PSA portal if process fits. Build when clients need branded experience, complex approvals, or integrations your PSA will never offer.
FC-09 CRM Fit Review helps when the question is build vs buy vs extend existing CRM.
Focused portals often land $15,000–$35,000 over 6–10 weeks with weekly demos. North Ark delivers senior full-stack — no offshore handoff chain.
See custom applications and Build service for fixed-scope entry points.
