Customer Portal
Let Customers Answer Their Own Questions
"Where is my order", "can you resend the invoice", "what is the status" - the same handful of questions, arriving by email and WhatsApp, answered by a person every time. A portal turns those into a login. Your customers get an answer at 22:00, and your team stops being a lookup service.
Key takeaways
- Start from the three questions your team answers most. A portal built around everything gets used for nothing.
- Access control is the entire security surface: every query must be scoped to the logged-in customer, server-side.
- Adoption follows the login. Magic links beat passwords for customers who visit twice a year.
- A portal that only reads is still worth building. Letting customers change things is a second, later decision.
What I build
- Customer login with roles, and every query scoped server-side
- Order, project or ticket status pulled live from your systems
- Documents and invoices the customer can download themselves
- Forms and requests that land straight in your workflow
- Notifications by email or WhatsApp when something changes
- Hebrew RTL and mobile-first, because most customers open it on a phone
How it works
A short scoping call
What hurts today, what you already use, and what "done" looks like.
A written fixed-price quote
Scope, price and timeline in writing, approved before any work starts.
Built in stages, on your real data
You see a working first version early, not a demo at the end.
Handover with documentation and monitoring
You own the code and the data, and a support window follows launch.
Working with me from the US or Europe
- Most of my client work is for companies in the US, UK, Germany, the Netherlands and Australia.
- Calls are in English and scheduled in your time zone. My working day covers most of the European one and the US East Coast morning.
- A fixed price in US dollars, agreed in writing before any work starts.
- Pay me directly, or hire me through Upwork if you prefer to work through a platform.
- You own the code and the data, with documentation and a support window after launch.
Guides on this
Practical guides from real client work.
Custom Software vs Off-the-Shelf: When a Small Business Needs a Custom System
Custom software vs off-the-shelf is rarely about features. I break down when SaaS is right, when you have outgrown it, and a clear build vs buy framework.
From Idea to MVP: How to Build an MVP (And What It Costs)
A practical guide to how to build an MVP: scoping must-haves vs later, realistic MVP development cost and timeline, and how AI now ships your idea in weeks.
Hiring a Developer to Build Your MVP: Freelancer vs Agency vs In-House
Hiring a developer to build your MVP? A practical comparison of freelancer vs agency vs in-house on cost, speed, risk, and control, plus red flags and how to structure the deal.
Signs Your Business Has Outgrown Spreadsheets (Time for a Custom App)
Has your business outgrown spreadsheets? The concrete signs it is time to replace spreadsheets with a custom app, the real cost and timeline to build one, and how AI made it affordable.
No-Code vs Custom Code for Building Your App or MVP
No-code vs custom code for apps: what each is good at, real cost and speed early vs total cost of ownership, the no-code ceiling and lock-in, and when to pick which.
How to Validate Your Idea Before You Build It
How to validate a startup idea before building: why validation saves money, talking to real customers, the smoke test, pre-sales, a manual concierge version, and the signals that justify building.
What Is an MVP, Really? Common Mistakes Founders Make
What is an MVP, really? A clear definition of minimum viable product, what an MVP is not, good vs bad examples, and the most common mistakes founders make.
How to Choose the Right Tech Stack for Your MVP
How to choose a tech stack for your MVP without overthinking it: the principles that matter, a sensible default stack, when to deviate, and what not to optimize for too early.
Is Vibe Coding Production-Ready? A Developer's Honest Take
Is vibe coding production-ready? An honest developer's take on what vibe coding is great at, where it breaks, and a prototype-vs-production checklist.
Frequently asked questions
Will customers actually use it?
Only if it is faster than sending you a message. That means a login they do not have to remember, the answer on the first screen, and a link to it in every email and invoice you already send. Portals fail on adoption, not on features.
Is it safe to expose our data this way?
It is safe when authorisation is enforced on the server for every single request, not in the interface. The common failure is a portal where changing an ID in the URL shows someone else's invoice. That is the thing to design against and to test for explicitly.
Can it connect to the systems we already use?
That is usually the point. The portal is a view onto your CRM, ERP or invoicing rather than a fourth place to keep data. Where a system has no API, the integrations page describes the options and their trade-offs honestly.
Sources
Official documentation you can verify the claims on this page against.
Let us scope your project
Tell me what you need and I will give you an honest scope, price, and timeline.