Scoped from how you really work
You describe the job as it happens today, the exceptions and the spreadsheet gluing it together, not a feature list. We write down what it must do before anything is built.
OCTIS HK • Software development
Custom software nobody has to retype numbers into
We scope it from how your work really runs, build it inside the account that already holds your accounting and customers, and hand it over documented.
- It reads your real records, not a copy typed in separately
- Working screens shown early, so a wrong turn is caught before it is built
- Bugs found in the first 90 days after launch are fixed at no extra cost
Why OCTIS
Built where your records already are
It is built inside the same account as your accounting and customers, so it reads the real record instead of a copy. Update a record once and the tool sees the same version.
You see it early
We build in stages and show working screens as it takes shape, so a wrong turn gets caught before it is built, not after the invoice.
The code, account and infrastructure are yours
We hand over all three, documented, so you are never locked into a system only we can maintain.
We tell you when off-the-shelf will do
If an existing tool already covers most of what you need, buying it is cheaper and faster than commissioning something custom. We say so, even though a custom build pays us more.
A plan that fits everyone
Teams held together by spreadsheets
When spreadsheets and generic apps stop keeping up, you need software that fits your process, not one you bend your business to fit.
Owners whose new tool does not know the books
You paid to build it and somebody still retypes the numbers. A tool built inside the same account reads them for itself.
Businesses with an idea for an internal tool
Dashboards, records and actions your team uses every day. We start by understanding the work in plain terms, no jargon.
What you get
From the first description of the job to a tool that is yours, you receive:
- A scope written from how the work really happens, before anything is built
- A fixed-scope project with an agreed price and timeline, or a dedicated team on a monthly retainer
- A prototype and working screens shown early, then staged builds you can steer
- A custom web application built to your workflow
- Connection to your accounting and customer records, so nothing is retyped
- User roles and permissions, so the right people see the right data
- The code, the account and the infrastructure handed over, documented
- Bugs found in the first 90 days fixed at no extra cost, and new features quoted separately
HOW IT WORKS
From the job as it happens to a tool that is yours, in four steps
01
You describe how the work happens
The process, the exceptions and the spreadsheet or tool gluing it together today. Not a feature list.
02
We scope, prototype and agree the price
A fixed-scope project with an agreed price and timeline, or a dedicated team on a monthly retainer. The number exists once the shape does.
03
We build in stages and show you
Working screens early, so a wrong turn is caught before it is built. Open questions sent back to you move the timeline most.
04
It launches, with 90 days on us
Bugs found in the first 90 days are fixed at no extra cost. A new feature is a new quote, not a warranty claim.
Not sure you need custom software?
Tell us how the work happens today. We tell you honestly whether a custom build fixes it, or whether something off-the-shelf already would.
Build on top of the same team
Automation, an app for your customers and managed IT support come from OCTIS's own IT team.
WHAT YOU BRING
What we need from you
1A description of the job
How it happens today, exceptions included, rather than a feature list.
2Where the real numbers live
The customer list, price list or stock count that holds the true version. Data that was never kept still has to be collected before a tool can read it.
3Someone who answers quickly
A build stalls on an unanswered question far more often than on anything technical.
FAQ
What is the difference between custom software and an off-the-shelf tool with my logo on it?
Custom software is built from scratch against your specific process. A rebranded off-the-shelf tool runs the same system as every other customer, just skinned differently. If an existing tool already covers most of what you need, buying it is usually cheaper and faster, and we say so before scoping a custom build.
What decides the cost of a custom software project?
Scope and complexity: what the software must do, how many systems it reads from, and how much back-and-forth the decisions take. That is why bespoke builds are quoted per project. Two ways to engage are usual, a fixed-scope project priced and timed up front, or a dedicated team on a monthly retainer. We scope the real requirement before naming either.
Who owns the code and infrastructure after the build?
You do. In a properly structured engagement the code, the account and the infrastructure it runs on transfer to the buyer. We hand over all three, documented, so you are never locked into a system only we can maintain.
Why do custom-built tools often end up disconnected from a company's records?
Usually because the developer's engagement starts and ends with that one build, so it has no reason to hold the rest of the company's data. It takes whatever it is handed on trust, and someone then keeps a second copy updated by hand. We build inside the same account as your accounting and customers, so the tool reads the real record instead.
What does the 90-day warranty cover?
Bugs found in the first 90 days after launch, fixed at no extra cost. New features and scope changes are new work, not a warranty claim, because the warranty covers what was built, not what gets added to it.