If they log in every day, it isn't a website.
Internal tools, client portals, and workflows a contact form can't carry. We build the web app first. Mobile when the work is in someone's pocket.
- Web appthe default
- Mobilewhen the job is on a phone
- R25 000internal tools from
A website is not the system.
If the real work lives in a spreadsheet, a WhatsApp group, or three logins that don't talk, a prettier homepage will not fix it.
- The spreadsheet is the product. One wrong copy and last week's numbers are gone.
- The handoff is a WhatsApp. Nobody can see the status except the person who sent it.
- The people doing the work are on a phone, and the "system" is a desktop site.
- Three tools, none of them sharing a login or a record.
- The owner is the only one who knows how it works. If they're off, the work stops.
- You paid for software that almost fits, then you work around it in a second spreadsheet.
An app is the process, on a screen, with one login.
How we build it.
Map the workflow first
Who logs in, what "done" looks like, where it dies. No screens until that's honest.
Web apps
Dashboards, portals, bookings, the internal tool the team actually opens. This is the default — it runs in a browser, on every desk.
Mobile when it earns it
If the work is in the field, on a site visit, or in a queue, we add a mobile app. Not a second product — the same system, in a pocket.
Logins that match the job
Staff see their work. Clients see theirs. Nobody shares a password to "just check something".
Wired to the rest
Forms, the CRM, the site, the inbox — connected where it saves a copy-paste, left alone where it doesn't.
AI where it earns it
Automations, Claude, website chat, a phone that answers, or AI inside the app. We'll say which. People keep the exceptions.
AI workflows →App types
What's in every build.
- A map of the actual workflow before we write a line of code
- A web app as the default
- Mobile when the work is on a phone
- Logins for staff and clients — not one shared password
- Connected to the site, CRM or inbox where it saves a step
- Starting prices — the quote is on the actual workflow
Stop running the business in a spreadsheet and a WhatsApp chat. The team logs in, sees the queue, and knows what is done.
- Replaces the shared sheet as the source of truth
- Each person logs in to their own work
- Status anyone on the team can see — not whoever last replied
- Opens in a browser, on every desk
- Hosting quoted separately
Clients check their own jobs instead of calling you. You stop being the person who "just looks it up".
- Everything in Internal tool
- Clients log in without a staff password
- They see their jobs and status — not your whole system
- Cuts the "just checking" calls
- Hosting quoted separately
If the work happens on a site visit, pinching a desktop site on a phone is not an app.
- Same system in a pocket — not a second product
- Built for field work, queues, and site visits
- iPhone and Android when people actually work from a phone
- Update the job without going back to the office
- Hosting quoted separately
Prices are set in South African rand. Dollar figures are an approximate conversion — we quote in your currency.
These are starting prices. The quote is on what it has to do, who logs in, and whether it needs a phone. Hosting is separate.
Not sure which one it is? Send the process and we'll say.
Get a quoteWork
Work we built and still run.
Questions we get about app development.
How is this different from a website?
A website sells and explains. An app is the work — logins, records, status, the thing people use every day. If you need pages and a form, that's web design. More →
Do you build iPhone and Android apps?
When the job needs them. Most products start as a web app. We add mobile when people genuinely work from a phone, not because an app store listing sounds good.
Can it talk to Linkssi or our current site?
Yes, if that's where the leads or the content already live. We don't rebuild a stack you already have working. More →
How is this different from AI workflows?
App development is the system people log into. AI workflows is automations, Claude and tools you already use, website chat, a phone that answers, and AI inside those apps. Sometimes it's the same build — we'll say which before you pay for both. More →
Do you have a starting price?
Internal tools start at R25 000. Client portals from R45 000, mobile from R65 000. The quote is on the actual workflow.
How long does it take?
It depends on the workflow. We'll tell you the shape of it before we quote — not a date we can't keep.
Can you work with what we already have?
Yes, if it's worth keeping. Send us what you use now and we'll say whether to keep it, connect it, or start again.
Who looks after it after launch?
We can. Hosting and a care arrangement are separate from the build, same as a website. More →