We build one system that your whole team works in, instead of spreadsheets and chat threads, with a documented database and permissions for each role. We start with one working module and add the rest in stages.
In many companies, information is spread across Excel files, chat threads and the memory of individual employees. Each department then works from its own version of the figures, management waits for someone to collect them by hand, and nobody can say for certain which version is right.
We design a system around the way your business actually runs: sales, purchasing, customers, stock, branches, employees, tasks, invoicing and collection, with management reports drawn from the same data. Each employee sees what belongs to their role and branch, and edits only what they are allowed to edit. Underneath sits a database, in PostgreSQL or MySQL, that we design, document, tune and prepare for backup.
If you already have an older system, we do not start by tearing it down. We study it, then extend it, improve it or migrate its data, whichever suits your case. Either way, the first release is a single module that works and is reviewed before we build the next one.
We design and build systems tailored to how each organisation works.
A customer or an invoice is typed into more than one file. The copies drift apart, reports stop matching, and the team stops trusting the figures.
When that person is away or leaves, the team cannot tell where an order, a purchase order or a collection stands, and the search through old messages begins.
Either everyone sees prices and customer lists, or nobody can finish a task without your approval, which turns you into a bottleneck in every process.
Management waits at the end of each period while someone gathers figures from scattered files. The reports arrive late and may be incomplete.
Screens are slow, a change in one place disturbs another, and there is no backup that anyone has actually tried to restore.
Each deliverable has written acceptance criteria, and you review it before you pay the instalment tied to its stage.
A drawing of how sales, purchasing and stock run today, who does what, and which module is built first. It is the reference against which delivery is measured.
Documented tables and relationships in PostgreSQL or MySQL, with clear names, so that any developer after us can understand and build on them.
A complete module, such as sales and invoicing or stock, running first on test data and then on your data, and shown to you before the second payment.
Who views, creates, edits and approves, for each role and each branch. You review it with us and approve it before it is switched on.
Your files or old-system data are imported to a test copy first, with a sheet that compares counts and totals against the source before any final move.
The reports we agreed at the start, built from the system's own data, or from a dedicated reporting database when the need calls for it.
A written backup routine with a tested restore, a concise documentation file and a handover walkthrough. The accounts are opened in your name.
Five steps. At each one there is something for you to review or approve before we move to the next.
After a free call, we run a paid 5-working-day diagnostic for the custom system, reviewing files, the current system and workflows. You receive a written report, an agreed illustrative deliverable, 3 priorities and an implementation offer with scope and acceptance criteria.
Your part: You review the report and decide whether to start the project. If it starts within 30 days of delivery of the diagnostic report, the diagnostic fee is credited in full.
We write a fixed-price offer that defines the scope, the milestones and the acceptance criteria for each milestone, and we make the first release a single module.
Your part: You approve the scope and acceptance criteria in writing and pay the first instalment (40%).
We design the database and permissions, then build the module in milestones and show you a working version while the work is under way.
Your part: You try the working version with your staff and write down your comments. When the preview is shown, the second instalment (30%) is due.
We take a backup, rehearse the data migration on a test copy, and test the system with cases from your own work before delivery.
Your part: You review the reconciliation sheet and test results, and accept delivery in writing against the criteria. Then the final instalment (30%) is due.
After the final payment we hand over the final files and documentation and leave the temporary accounts. We fix defects free of charge for 14 days after delivery, then an optional monthly maintenance plan is available.
Your part: You receive the accounts and files in your name, and decide whether to add the next module under a new written offer.
The entry point is the diagnostic: 5 working days at a fixed price, producing a written report, three priorities and a fixed-price implementation offer. The diagnostic is paid upfront and credited in full against the project if it starts within 30 days of delivery of the diagnostic report. After that we build one module first, and we never ask for the full project fee upfront.
For complex work that needs assessment before implementation can be priced. Deliverables are agreed before the start; simple services begin with a free call and a written offer.
Often, yes. We start by reviewing the system and its database, then state in the report what can be developed and what deserves replacing, and why. If adding modules, improving performance or connecting the system to other tools is the better route, that is what we propose. If replacement is better, we say so in writing with our reasons, and the decision is yours.
Because one module can be tested on your real work before we build on top of it. You review it with your team, find what needs to change, and then we add the next module under a written offer with new acceptance criteria. This limits the risk and keeps you from paying for parts you have not tried yet.
Yes, this is core to the work. The permissions matrix defines who views, edits and approves, for each role and each branch, so a branch manager sees their branch and management sees the whole picture. Large multi-branch systems are accepted after a paid diagnostic and a written scope, starting with a small first phase before any expansion.
We take a backup before any migration, rehearse the move on a test copy first, and then compare counts and totals against the source. Your customers' personal data stays in your own accounts, and we do not place it in any external tool or service without your written consent. We work with temporary permissions and leave them after handover.
In three instalments tied to progress: 40% at the start, 30% when a working preview is shown, and 30% on acceptance and approval. You see the evidence for each stage before you pay for it, and we never ask for the full project fee upfront. Anything outside the written scope is priced before we carry it out.
You own everything we deliver. Hosting, licences and domains are opened in your name and priced separately. After delivery we fix defects free of charge for 14 days, then an optional monthly maintenance plan is available. We do not promise particular business results; our commitment is written into the contract: defined deliverables, tests before handover, and dates.
Tell us how your team works today and where it gets stuck. We will agree the starting point with you and offer the diagnostic at a fixed price.