Customer portals & accounts
Give customers a place to sign in, submit information and follow progress. We define what each person can see and do, how information is stored and how your team manages it.
Auckland developer · Working across New Zealand
Custom web applications that fit how you work.
A customer portal. An internal tool. A connection between systems that saves your team copying the same information twice. I build the interface, backend and integrations as one working product.
Daniel Olliver · Full stack developerDirect contact from scoping through deployment.
Start with the problem you need to solve.
Sometimes an existing platform will do the job. A custom application makes sense when your workflow, users or integrations need something more specific.
Internal tools & workflows
Turn a spreadsheet-and-email process into a shared application: submissions, approvals, scheduling or a useful view of operational data. Start with the workflow causing the most repeated work.
API & payment integrations
Connect a website or application to another service. That can mean payments, booking tools, transactional email or synchronising data. I check API access and limitations before recommending the approach.
Existing application development
Add a feature, investigate an unreliable workflow or improve a React/Node application. The first step is understanding the codebase, its data and the way changes reach production.
Only need a public website? A custom application may be more than you need. Explore small-business websites, online stores or a website redesign for a simpler starting point.
Experience beyond the brochure site.
My work spans complete client builds and features shipped inside an existing product team. Here is what I contributed.
Delivered a patient-facing assessment platform for a UK healthcare provider during a three-month contract. React frontend, Node/Express backend and Supabase PostgreSQL, deployed into commercial production.
Private client systemA New Zealand property-listings platform with agent submissions, an admin approval workflow, buyer alerts, online payments and transactional email.
Private client systemBuilt and shipped features in a live React/Node scheduling product for construction trades. Worked within an existing team, with sprint cycles, code reviews and production delivery.
Commercial product contributionSee my development portfolio for more on the stack and public example applications, or read the Back to Nature Tours booking and CMS case study.
One developer, across the full stack.
The tools follow the requirements. I work primarily with JavaScript and TypeScript, and make the trade-offs clear before committing you to a platform.
Frontend
React, Next.js, TypeScript, HTML and CSS. Responsive interfaces, understandable forms and clear loading, empty and error states.
Backend & data
Node.js, Express, REST APIs, MongoDB and Supabase/PostgreSQL. Data models, validation, authentication and permissions designed around the application’s users.
Connections
Experience with Stripe, Google APIs, Webflow CMS and FareHarbor bookings. We check the external service, subscription requirements and failure cases as part of scoping.
Delivery & handover
Git, deployment and account access, with a documented handover. Hosting, backups, monitoring and ongoing maintenance requirements are agreed for the specific project.
A clear route to a useful first version.
We define a manageable first release, test the important journeys and leave room to learn from people actually using it.
- Map the workflow and constraints
Who uses it, what they need to do, what data it handles and which systems it connects to. For an existing app, I review the code and deployment process first.
- Agree the scope and quote
Define the screens, roles, integrations, acceptance criteria and delivery stages. Identify third-party fees, client inputs and the work that can wait.
- Build, review and test
You see working progress and give feedback. Testing covers the critical journeys, permissions, validation and integration failures relevant to your project.
- Launch and hand over
Deploy the agreed release, confirm access and document how it runs. Decide what support and future improvements you want to arrange.
Scope first. Then a useful quote.
A portal with one user role and one integration is a different project from a system with multiple permissions, migrated data and complex rules. I quote around that difference.
Send a short outline: the workflow you want to improve, who will use the app, any existing software, your ideal timing and an approximate budget if you have one.
I’ll explain the likely approach and what needs investigating before a fixed scope can be priced. For a larger build, we can agree separately quoted stages. Hosting and third-party subscriptions are identified separately.
Do I need a custom web application?
Not always. If an existing booking platform, store or form can handle your process well, that may be the sensible choice. Custom development becomes useful when the gaps create repeated work, limit the customer experience or stop systems sharing information.
Can you connect to our existing software?
Often, where it provides a suitable API or supported integration. I check the available access, documentation, data formats and service limits before promising a connection.
How much does a web application cost?
It depends on the workflows, user roles, integrations, existing code and data migration. I prepare a project-specific quote after defining the scope. The website cost guide covers simpler website projects; application work needs its own estimate.
How long will development take?
We agree the schedule once the first release is defined. External access, content, feedback and integration complexity all affect delivery. Larger products can be broken into stages with a usable first release.
Who owns the code and accounts?
The agreement sets out the custom code and deliverables you receive. Your service accounts should be under your control. Third-party services and open-source components retain their own licences, fees and terms.
Do you work with clients outside Auckland?
Yes. I work remotely with businesses across New Zealand. For Auckland clients, meetings at your business can be arranged by appointment. You deal directly with me throughout the project.
Let’s make the next part of your business work better.
Tell me what you’re trying to build or improve. I’ll reply personally with a practical next step.