What we build
Datum Forge builds one business system per client, in place of the rented tools, spreadsheets and rekeying a growing company ends up running on: software designed around how that business actually works and built from standard parts already hardened in use, powered by AI where AI earns its place, and run on accounts in the client’s own name. It is not a chain of rented tools and not a set of agents: the scripts, scheduled jobs and links between tools are built into the system itself. It starts with the problem that costs the most and grows from there.
What “a system” means
A chain of rented tools moves data between services you pay for, and breaks when one of them changes. An agent does one task inside one tool, on a subscription, and you get another one for the next task. A system holds your records in one place, does the work end to end, and is yours. The scripts, scheduled jobs and links between your tools that keep it running are part of it, not rented on the side.
The difference shows up in three questions: who owns the customer record, whose name the accounts are in, and what happens when a tool underneath changes. With a stack of rented tools the answers are the vendors, the vendors, and you find out on the invoice. With a system built this way the answers are you, you, and we change one part while the rest keeps running.
What changes is concrete: the record is kept once, the rekeying stops, and the hours it took go back to the work the business is for. What you do with those hours is yours to decide. We do not promise a return, and nobody honestly can.
How it is put together
Every system is designed around how your business works, and none is built from scratch: it is assembled from standard parts we have already hardened in use, with your own process on top, so what every business needs is proven before yours relies on it and the design goes into what is yours alone. The finished system runs on one hosting account, one database and one set of accounts, all in your name.
Which providers sit underneath (hosting, database, email sending, AI model) is named in the design, not on this page, because the right answer depends on your business and not on our preferences. The software is ours, licensed to you; your data, your content and anything we build only for you are yours. What you own, in full.
Three shapes of pain we recognise
An engagement usually starts with whichever one is costing you most. Often enough, two of them turn out to be the same underlying problem wearing different clothes.
Data that lives in five places
Your team rekeys customer information into your CRM, your accounts system, your fulfilment tool, and two spreadsheets. The system holds the customer record in one place and pushes it to each downstream tool in the shape that tool needs.
Quoting that loses deals
A quote takes three days to produce because two people rekey the same numbers into three systems and email a PDF back and forth for approval. The system pulls the numbers from source, applies your pricing rules, and gets the quote out the same day.
Week-long month-end
Someone spends three days of every month reconciling exports from four tools into the report the business is run from. The system produces that report on the first working day of the month, in the format its readers already use.
These are three shapes we see often, not a list of the three things we do, and they are drawn from the founders’ own shipped work rather than from Datum Forge case studies. If your specific pain is not on this page, that is not a signal we cannot help; it is a signal the first call is the right next step.
Not every job is a system. A smaller, defined job is welcome too: a fix, a script, a job that runs on a schedule, a link between two tools you already use, or a change to an app your team built. It skips the design stage. Describe it on the contact page and we quote it in writing before we start.
Who this is for
We build for businesses small enough that nobody’s job is to look after the list of software the business pays for.
The signs are usually plain: several tools doing one job between them, the same record typed in more than once and seats still paid for people who left or never logged in.
Who this is not for
Consumers, and enterprises who want an embedded team of twenty.
Questions
- What is a business system, as opposed to a chain of rented tools?
- A system holds your records in one place, does the work end to end, and is yours, on your own accounts, with its scripts, scheduled jobs and links between tools built in. A chain of rented tools moves data between services you pay for, and stops when one of them changes.
- Do you build AI agents?
- We build systems that use AI where it earns its place. We do not sell agents by the seat, and we do not add a subscription for each new task.
- Can the system grow after the first problem is solved?
- Yes. It is modular, so the next job extends the same system instead of adding another tool that does not join up. New scope is scoped and priced as new work.
- Is every system built from scratch?
- No, and not from a template either. Each system is designed around how your business works, then built from standard parts we have already hardened in use, so it fits you without starting from nothing.
- What size of business is this for?
- We build for businesses small enough that nobody’s job is to look after the list of software the business pays for. Not consumers, and not enterprises wanting an embedded team. Small, defined jobs are welcome too, quoted in writing before we start.
- Is there a job too small for you?
- Not if it is defined: a fix, a script, a scheduled job or a link between two tools. It skips the design stage, and we quote it in writing before we start.