One system for every branch, connected to the software you already run
Several branches, several roles, and software you already depend on. I don't put one fixed number on all of that. I split the work into stages, and the first stage has to be something your people actually use.
This is for you if any of this sounds familiar
You have an IT team and the problem is still there
When a clear problem sits unfixed for a year, it usually isn't skill. The team is holding up what already exists and never gets a clear week to build anything new.
Each branch does the job its own way
With no shared system, every branch invents its own method. The numbers at head office never add up, and nobody can say which branch is right.
There's an old system you can't throw away
Accounting software or an ERP that has run for years usually has to stay. The real job is making the new system talk to it, not ripping it out.
A big project already burned you once
Large builds fail when everything ships at the end and nobody uses anything for a year. That's why I stage the work so something is live early.
Three packages. Pick the one that matches what you actually need
These are full project prices, not starting points that grow later. If anything falls outside the scope, I tell you the number before I start on it.
- I pick the one thing costing you the most and build that first
- Live with one branch or one team, on real work, not a demo
- Database and structure sized for the branch count you'll have later
- Before and after numbers, so you can see what actually changed
- Written contract in English: scope, delivery dates, and who owns the code
- README and code comments in English, so your developers can read the work
- 60 days of support once it goes live
- The other branches are not moved over at this stage
- The rest of your branches move onto the same system
- Roles and permissions that match how the company is actually run
- Connected to the accounting system or ERP you already use
- Reports that compare branches side by side, for the people who have to compare them
- Training for the staff who use it, scheduled inside your working hours
- Full English documentation: user guide plus a technical write-up for your IT team
- Replies inside a set window in your time zone, agreed before the work starts
- 60 days of support after each branch goes live
- A mobile app for the people working away from a desk
- Analysis and forecasting from the data the system has collected by then
- An API so your other systems can connect in
- Code sitting in your company's own accounts, with the full commit history
- Every part written up in English so your IT team can take it over completely
- 60 days of support, then your team runs it without me
Not included in any package, and I am telling you before you pay
- One fixed price for the whole thing before anyone knows the real scope. Any number I gave you today would be wrong, and you would be the one paying for it.
- Hourly billing. I write down the scope and the full number for a stage before that stage starts.
- Guarantees about your sales or your profit. I guarantee what I control: scope, delivery dates, and how fast I reply.
- Replacing your IT team. I work with them and hand the system over so they can run it. I'm not there to take their jobs.
- Cloud, licence, and third-party fees. Those go on your company's own accounts at cost, and I list them for you before you commit to anything.
How it works, from first message to launch
Tell me the problem, not the feature list
Start with where the money or the hours are going. I'll push back on what should be fixed first.
I send the first stage in writing
Scope, price, delivery date, and what counts as done. In English, one document, with no extra costs appearing later.
The first stage goes live
Payments follow what has actually been delivered. You can stop at any point and still keep working software and all of the source code.
You look at the results, then decide about the next stage
If the first stage didn't pay for itself, don't continue. That is the whole reason I work this way.
Questions people ask about this service
Why won't you quote the whole project up front?
A number given before anyone knows the real scope is always wrong, and you pay for it either way: through overruns, or through me quietly cutting quality to stay inside the budget. So I quote one stage at a time, and the number for that stage is fixed and in writing before it starts.
Can one person handle a system this size?
For work this size I bring in people I have worked with before, but I am the only one responsible and the only one you talk to. Staging the work is part of the same answer: you are not betting the whole project on me on day one.
We already have an IT team. How does that work?
I work alongside them, not over them. The code goes into your company's own repository accounts, and the README, comments and documentation are in English so your developers can pick it up and keep building. The goal is that they don't need me.
What if the first stage isn't what we wanted?
You stop. You still have one working piece of software and all of the source code, so someone else can carry on from there, and the 60 days of support still runs from the day it went live. That is the trade against signing for everything at once and waiting a year to find out.
Our business data is confidential. How is that handled?
Sign an NDA before any details change hands, that's normal and I have no problem with it. The design also keeps your data in your company's own accounts from the start, not on anything of mine.
Where are you based, and when can I reach you?
I'm a developer working on my own from Thailand. No company, no team, no sales staff, and no security certifications, so if any of that is a requirement on your side it's better to know now. Before anything starts I give you the hours I'm reachable, converted to your time zone, and I keep to them.
Often booked together
Tell me the problem first. Features can wait.
Where is the money or the time going right now? Start there and I'll tell you what I would fix first.
Happy to sign an NDA before any detail is shared.
A written brief is the easiest way to start. I'll come back with what the first stage should be, and what it costs.