Web app development: Web apps built around how your team works.
Customer portals, booking flows, dashboards and internal tools, connected to the systems you already run and built in a 4-week sprint: a clickable prototype in week 1, the build on your data in weeks 2–3, production and handover in week 4. You talk to the technical lead and own 100% of the source code.
Customer portal. Customers check the orders held in your ERP, pay the invoice online and get the receipt by email.Booking flow. Open slots come from the database you already run, the deposit goes through your payment gateway, and the confirmation goes out by email.Admin dashboard. Sales from the ERP and bookings from the older database on one screen, with a summary emailed to managers.Internal tool. Staff approve refunds from one queue. Each decision is written to the ERP, logged with who approved it, and the customer is emailed.
What we build, layer by layer.
The pages your customers use, the tools your team works in, and what connects and runs them. Every deliverable has optional AI behind ✦ Explore AI features: AI prepares drafts, your team approves them, and every screen still works with AI switched off.
01
In front of your customers
What customers and visitors use, on your own domain.
your-company.com/portal✦ AI
Customer portals and booking flows
Customers sign in to book, order, pay and check progress themselves, instead of calling or messaging your staff.
Customer accounts with secure sign-in
Booking with live availability, deposits and reminders
Orders, invoices and payment by card, bank transfer or e-wallet
Status pages, with updates by email or WhatsApp
In the languages your customers use
On request
Sign-in by passkey, email link or SMS code
✦ Optional AI
Booking assistant on WhatsApp and webAnswers from your own availability and prices, drafts bookings for customers to confirm, and hands over to staff with the transcript.
Uploaded documents into form fieldsDocuments customers upload, such as invoices or application forms, are read into the form, and staff confirm the fields before saving.
Reply drafts for your staffReplies to customer messages drafted from live order and booking data, in the customer’s language, for staff to send.
The public site that explains what you do: static pages that load quickly, are easy for search engines to read, and are edited by your team.
Static pages served from a CDN near your visitors
Pages and posts your team edits without a developer
Titles, structured data, sitemaps and analytics from day one
Enquiry forms to your inbox or CRM (customer relationship management) system, with spam filtered and no CAPTCHA puzzle
Language versions for each market
✦ Optional AI
Answers from your own pagesVisitors’ questions answered from your own pages with a link to the source, and a plain “not covered” when the answer isn’t there.
Enquiries sorted, replies draftedForm enquiries sorted by type and urgency, with a reply draft your team edits and sends.
Translation draftsPages drafted in Bahasa Indonesia, Bahasa Melayu or Chinese from your English copy, checked by your team before publishing.
Image descriptions and meta draftsAlt text and meta descriptions drafted for each new page, approved by your editor before they go live.
We put the app live under your company’s accounts, set up error monitoring and backups, and hand over everything the next developer needs.
Hosting on Cloudflare, AWS, Azure or Google Cloud, in your company’s name
Staging and production, with a staging link for every weekly demo
Automatic deploys from your repository, with rollback
Error monitoring, uptime checks and backups
Source code, documentation and admin access at handover
On request
Runbooks for the team that keeps it running
Running costs of each third-party service written down
✦ Optional AI
Error summaries for the on-call developerNew errors grouped and summarised with recent changes and likely causes, for the developer on call to confirm and fix.
Release note draftsPlain-language notes on what changed in each release, drafted from merged work and edited before your team sees them.
Documentation kept currentChanges to the code prompt draft updates to the handover documents, reviewed by the developer before they are merged.
Monthly cost write-upUsage and third-party bills totalled in code; AI explains what changed from last month and which service caused it.
For companies in Singapore, Malaysia and Indonesia, in English and Bahasa Indonesia. You talk to the technical lead throughout, from the first call to handover.
4 weeks · 3 steps
Week 1Week 2Week 3Week 4Week 1
Week 1
Listen, understand & prototype
We listen to the people who do the work, map the problems to solve and deliver a clickable prototype of the main screens by the end of the week.
Week 2–3 · 2 weeks
Core build
We build the core features and integrations on your real data, and demo them on a staging link every week.
Week 4
Live production & handover
We deploy to production and hand over the source code, documentation and admin access.
How we work
Built on your real data
We connect to your database, ERP or APIs from week 2, so every demo shows your own records rather than placeholder content.
Fast on ordinary devices
We keep pages light, so they load quickly on the laptops and phones your staff and customers already have, including on mobile data.
A stack your team can keep
React, Next.js, Astro, Go, Laravel or .NET, chosen for what your team or the next vendor can maintain after handover.
Yours from the first commit
The repository, hosting and third-party accounts sit under your company. At handover you get the source code, documentation and admin access.
Have a web app in mind? Talk the scope through with our technical lead.
Web applications with real users and real data: customer portals, booking and ordering flows, dashboards and internal tools. We also build marketing sites when they sit alongside one of these.
Can you work with our existing systems?
+
Yes. We connect to whatever is already running, such as an ERP, a payment gateway or a legacy database, and we map those integrations in week 1 so the demos from week 2 show your own records.
Can you add AI features to our web app?
+
Yes, as options on any part of it, such as answers from your own documents with the source linked, uploaded documents read into forms, or a weekly summary of unusual figures. Each AI draft waits for someone on your team to check it, and every screen still works with AI switched off.
Do we own the source code?
+
Yes. You own 100% of the source code from the first commit, and at handover you receive the code, the documentation and admin access.
Who will we talk to?
+
The technical lead who does the work, with a domain specialist who has done this kind of work before. We reply within 24 hours, there’s no account manager in between, and we sign an NDA on request.