Services
Software built around how your business actually works
We build web applications, internal tools and operations software for businesses that have outgrown spreadsheets. Small team, direct contact, and code and data that stay yours.
When a business usually calls us
- The work runs on a stack of spreadsheets that only one person fully understands.
- Off-the-shelf software covers half the process, and the other half is handled by hand.
- An earlier developer left, and nobody can safely change what they built.
What we build
Most of our work is web software your team opens in a browser, on the devices they already have. We quote each project after a scoping call.
Custom web applications
A system built for one business process end to end: records, roles, approvals, documents and reporting.
Internal tools and dashboards
Admin screens and reports that pull from the systems you already run, so your team stops exporting to spreadsheets.
Point-of-sale and operations software
Counter, kitchen, stock and day-end reporting for food businesses. Our own product, Hisaab, is live today.
Integrations and data work
Connecting accounting, payments, messaging and in-house systems, plus the data clean-up that usually comes with it.
AI features in your product
Drafting, extraction, classification and search over your own documents, with the limits and review steps written into the design.
Maintenance and support
Taking over an existing codebase: fixes, upgrades, documentation and a safe way to keep changing it.
Software projects are quoted after a scoping call, because the price depends on how much of the process you want covered. You get a written scope, a fixed price or a rate, and a delivery plan before any build starts.
How a project runs
Short stages, each ending in something you can open and judge for yourself.
- 1
Scoping call
We walk through the process you want covered, who uses it, and what has to be true on day one.
- 2
Scope and estimate
You get a written scope, a price or rate, a delivery plan and what we need from your side.
- 3
Design the flow
Screens and data model first, as clickable drafts, so changes happen before they get expensive.
- 4
Build in stages
We build in two-week stages. At the end of each one, you use what is there and tell us what to adjust.
- 5
Testing and handover
Testing with your real data, a trial run with the team, documentation and the keys to the hosting.
- 6
Support
A fixed monthly arrangement for fixes, upgrades and the next round of changes, or a clean handover to your own team.
Ways to work with us
Pick the one that matches how settled the scope is.
Fixed-scope project
A written scope at an agreed price, delivered in stages against a plan.
Best when you know what you need built.
Monthly team
An agreed number of days a month on your roadmap, re-planned at the start of each month.
Best when the work is ongoing or the scope is still moving.
Build and hand over
We build the first version, document it and hand the code and hosting to your team.
Best when you plan to hire developers later.
Support retainer
A monthly arrangement covering fixes, small changes, upgrades and monitoring.
Best for software that is already live.
Tell us what you need
A few lines about the work is enough to start. We read every enquiry ourselves.
- A reply from a person. Not a sales sequence.
- A written scope before any work. Questions, methods, deliverables, fee and dates.
- Your material stays yours. We work under a confidentiality agreement, and Draaftly never uses your data to train AI models. How we protect it
Thank you
Questions people ask
How much does a project cost?
It depends on how much of the process the software has to cover. After a scoping call you get a written scope with either a fixed price or a day rate, plus the delivery plan, before any build starts.
How long does it take?
A focused internal tool is usually a matter of weeks; a system that covers a whole process takes longer and is delivered in stages, so you are using part of it long before the last stage is done.
Who owns the code?
You do. On final payment the code, the repository and the hosting accounts are yours, with the documentation needed to work on it without us.
Can you work with our existing systems?
Usually yes. Tell us what you run and we will say plainly what can be connected, what would need replacing and what is not worth touching.
Will our data be used to train AI models?
No. Draaftly never uses your data to train AI models. Our AI providers, Anthropic and Google Cloud, do not use customer data from their commercial services to train their models by default. We explain this in full on our Trust page.
Can you maintain software someone else built?
Yes. We start with a short review of the code, hosting and risks, then give you a written view of what to fix first and what it would cost to keep it running.
Related
See the software we have built for ourselves, and the research side of the business.