Software, platforms, automation
We don't market software. We build it.
The One Plus is an engineering company. We build websites, mobile apps, software products, and automation — and the same people who write it keep it running afterwards.
Five things we do, one team. We run them on our own business first, then for clients.
-
5
Core capabilities
-
Products
Software many customers share
-
Automation
Systems talking to each other
-
Monitored
Live systems we keep running
What we engineer
Five practices. They ship as one system.
Each one is a real team with its own way of working, not a line on a menu. Most projects use three of them together.
-
Website Development
Websites and web apps built to be fast and to stay easy to edit. Your team gets a proper place to manage content — real fields, not one big text box — and speed is checked automatically before anything goes live.
- Marketing sites, with load speed measured not assumed
- Customer logins, portals, and dashboards
- A content setup your team can update without us
- Built in pieces, so a redesign is not a rebuild
-
App Development
Apps for iPhone and Android. We agree how the app and the server talk to each other before any screen is designed, because that seam is where mobile projects usually go wrong. Getting into the app stores is part of the plan, not a surprise at the end.
- One app for both iPhone and Android, or one each
- How the app and server talk, settled up front
- Works offline, then catches up when signal returns
- Push notifications, store submission, and crash reports
-
Automation
We connect the tools you already use so work moves between them without anyone copying and pasting. If a step fails, it tries again — and if it still fails, a person gets told rather than the data quietly disappearing.
- Connects the tools you already pay for
- Custom pieces where off-the-shelf runs out
- Failed steps retry, then alert a human
- Keeps sales, billing, and ops data in step
-
Chatbot
A chat assistant that answers from your own documents and price lists, not from guesswork. It stays inside what it actually knows, hands over to a person when it is unsure, and every conversation is saved so you can see what it said.
- Answers from your documents, with the source shown
- Says “I don’t know” instead of inventing an answer
- Hands over to a person, conversation attached
- Every chat saved so you can check and correct it
-
Platform
Software that serves many customers from one system, each seeing only their own data and their own branding. Includes the parts most builds skip: an admin screen for your team, usage tracking that feeds billing, and a record of who changed what.
- One system, many customers, data kept separate
- Your customers see their own brand and domain
- Control over who can see and do what
- Usage tracking, billing, and a full history
How we work
We run what we build.
The One Plus runs its own software. The automation that routes our work, the dashboard our team uses all day, and the products we license to others are all systems we keep running ourselves — the same ones we hand to clients.
That changes how we quote. We have already hit the awkward edge cases, so estimates include what a decision costs to live with, not just to build. And when something breaks at 2am, the people who wrote it are the ones who fix it.
Read how we deliver-
In production
Operations platform
Where our own delivery work lives: schedules, client updates, and who is busy with what. It runs on the same core we deploy for clients.
-
In production
Automation fabric
The workflows that handle new enquiries, routing, billing events, and reporting — with monitoring and retries we tuned against real failures.
-
In production
Shared component system
One shared set of design and code pieces, so a fix can land in several places at once instead of being redone each time.
Delivery model
Three stages. Nothing hand-waved.
Whether software ships on time is mostly decided before and after the code gets written. Three stages, each ending in something you can read.
-
Scope
A written plan: how it will be built, what it connects to, what the data looks like, and the milestones. Every open question gets answered before code starts.
-
Build
We build milestone by milestone against a test site you can open any time. Every change is reviewed and checked automatically.
-
Operate
We put it live with monitoring, written handover notes, and a named person to call. We stay on the systems we ship.
What we build with
- TypeScript
- React
- Next.js
- React Native
- Node.js
- PostgreSQL
- n8n
- WordPress + ACF
Next step
Tell us what needs building.
Send the problem, the limits, and the deadline. You get back a plan for how we would build it and a milestone schedule you can hold us to.