Custom Web Apps · dashboards, portals and admin tools
Retire the workaround. Give the work a proper home.
When a shared spreadsheet, an email chain and a copy-paste report hold a process together, a focused web app takes over. The right people see the right records, common actions become a click instead of a message, and your other systems stay in step.
Source access, ownership, licensing and handover are agreed up front in the engagement. The first version is built around one group of users and the job they do every day.
- Leak repair · new customerUnassignedNewAssign
- Quote follow-upPriyaQuotingDraft reply ready
- Quarterly service · repeat clientSamBookedSend reminder
- Warranty claimAlexWaiting on partsUpdate client
Synced withCRM · calendar · accounting (draft invoices)
AI assistDrafts follow-ups for a person to review
What we build
From the workaround you have to the tool you need
Dashboards, client portals, admin tools and the connected pieces in between. The shape comes from the work, not from a template.
TodayA shared spreadsheet tracks every job
Admin toolA workboard with owners, statuses and history, and clear rules on who can change what.
TodayClients email to ask where things are up to
Client portalClients sign in to see progress, upload documents and approve quotes.
TodayThe monthly report is stitched from exports
DashboardLive figures pulled from the systems you already use, filtered the way you read them.
TodayThe same details are typed into three systems
Connected toolEnter it once; it reaches your CRM, accounting or calendar through their APIs.
TodayApprovals happen by reply-all
Approval queueRequests wait with their context, and every decision is recorded.
The first version
Small on purpose, useful from day one
Before any code, we agree five things. Everything else goes on a ranked backlog for later.
- Users
- One group first, such as your office team or your clients, with sign-in and the right roles.
- Records
- The data the app owns or reads, and where each piece comes from.
- Actions
- The few things people do every day: assign, update, approve, upload, export.
- Connections
- CRM, accounting, Microsoft 365, Google Workspace or other tools with an accessible API. Feasibility and permissions are checked during scoping.
- AI, where it helps
- Drafting replies, summarising notes or sorting incoming requests, with a person reviewing the output. Optional, never decoration.
How it gets built
Working software early, real users before launch
Shape
Agree users, records, actions and connections, what is out of scope, and the main user journeys.
Build in slices
Each slice lands on a preview link you can click through, reviewed with the people who will use it.
Launch to the first users
Real work moves across. The old workaround stays read-only until people trust the new tool.
Hand over
Source access as agreed in the engagement, deployment notes and an admin guide are handed over, with the next-version backlog ranked.
Good fit
Worth a conversation if…
- A process lives in spreadsheets, inboxes or manual reports, and people work around it every week.
- You can name the first group of users and what they need to do.
- The data you need is in tools with an accessible API or export, or can live in the app itself.
- You want source access and handover terms agreed up front.
Not yet
Probably too early if…
- The idea has no first user group or owner yet.
- An off-the-shelf tool already does the job and only needs setting up.
- You are not sure which process to fix first. Agentic Consulting starts there.
Buyer questions
Custom Web Apps FAQ
Straight answers before you scope a build.
Have a question that isn't here? Ask it in the enquiry form. A few sentences are enough. Ask in the enquiry
What kinds of web apps does Nebulas build?
Internal workboards and admin tools, client portals, dashboards and reporting tools, intake and assessment forms, and connected tools that sit between your existing systems.
How big is a first version?
Small on purpose: one group of users, the records they need, and the few actions they take every day. Everything else goes on a ranked backlog for later.
How long does a first version take?
It depends on scope, data and integrations. Timing is estimated once the first version is defined, and progress is shown in slices on a preview link rather than revealed at the end.
How are source access and ownership handled?
Source access, ownership and licensing are agreed up front in the engagement, before the build starts. Handover includes deployment notes, an admin guide and a ranked backlog for the next version.
Can it connect to our existing tools?
Where the tools have an accessible API, webhook, export or approved integration path. Permissions, licences and feasibility are checked during scoping. CRMs, accounting tools, Microsoft 365 and Google Workspace are familiar examples.
Where does AI fit?
Only where it saves real effort, such as drafting replies, summarising notes, sorting requests or preparing reports. A person reviews the output.
What happens after launch?
Support is agreed as part of the engagement: who fixes what, for how long, and how changes are requested. Nothing is assumed.
What would you like to connect or improve?
A few sentences are enough to start. Request a workflow review and we will reply by email with a practical next step. No booking is made by submitting this form.
- Nebulas reviews your context.
- We check fit and urgency.
- We reply by email with the most practical next step.
We use your details to review and reply to this enquiry, and keep a record of it. Privacy details