Build it as a project
Right when you already know the problem and want a defined scope, a defined deliverable, and a timeline agreed before anyone starts.
When the business is running on six different spreadsheets
Orders in one place, stock in another, customer history in somebody's head. It holds together for a surprisingly long time, and then one day nobody quite trusts any of the numbers. I build the system that takes over from all that, starting with whichever part is costing you the most time right now.
Asking costs nothing, and you do not need a specification written first.
From chasing people for answers to opening it yourself
None of this has to happen at once. We take whichever one is wasting the most time and finish that properly first.
- Now
Orders arrive in five different places
Some come by message, some by phone, some over the counter. Someone copies them into one list at the end of the day, and that is where things go missing.
AfterOne order list
Every order lands in the same place regardless of how it came in, and you can see where each one is from the moment it arrives to the moment it ships.
- Now
The stock number and the shelf disagree
What the file says and what is actually on the shelf stopped matching days ago, and now nobody is quite sure which one to believe.
AfterStock people believe
What came in, what went out, what is left. Your sales team and your warehouse look at the same number instead of arguing about whose is right.
- Now
Customer history is scattered
Names in one place, phone numbers in another, what they bought last time in someone's head. A returning customer asks about a past order and nobody can find it.
AfterOne customer record
Contact details, order history, their agreed pricing, and anything outstanding, all in one place your team can search.
- Now
You find out who is doing what by asking
Every status update costs somebody an interruption, and whatever answer you get is out of date by the afternoon.
AfterWork you can see
Who owns each job, what stage it is at, what happens next. Nobody has to interrupt anybody to find out.
- Now
You wait on someone to tell you how the business is doing
You want to know what sold and what is running low, and somebody has to assemble a file before you can find out.
AfterNumbers you open yourself
Sales, what is outstanding, what is running low, and the overview you actually decide from. Open it whenever you want, without asking anyone.
The right size depends on the work, not on how big the company is
A five person shop can have genuinely complicated operations, and a large company can have exactly one thing that needs fixing. So I look at the problem itself, who has to use it, and what information has to join up, and we size it from there.
Fix the one thing that keeps costing you time
Good for a single job that eats hours or goes wrong often, like taking orders, producing a document, or chasing a status. Worth solving that properly first. You do not always need a whole system to fix one awkward step.
Get the team working off the same information
Right when several people rely on the same information, hand work between each other, and want to see where something stands without having to ask.
Connect the parts so you can see the whole business
Right when orders, stock, customers, and reporting have started to depend on each other, so the information has to flow between them and you need the view over the top.
Three ways this usually starts
Some people know exactly what they want built. Others need help working out what is worth building at all. And some already have a team and simply need another experienced pair of hands for a while.
Plan it with me first
Right when you are not yet sure what should exist. I look at how the work actually happens, put the pieces in order, and tell you honestly which parts you do not need to build at all.
Join your team on contract
Right when you already have a team and a clear plan, and want another experienced developer working alongside them for an agreed stretch of time.
If you already have a system that has stalled, or you need someone who can talk to both your team and your developers without anything getting lost, that is work I take on too. If it started as an AI generated site, here is what I inspect and repair.
What people ask before they start
Everything is in spreadsheets right now. Can that move across?
Yes, and honestly it is the best possible starting point. Your spreadsheets are a record of how your business actually works, which is worth more than any specification anyone could write for you. Send me a sample, I design around how you already work, and I bring the old records over. Nobody retypes years of data.
My team is not good with computers. Will they use it?
They will if it is built for them, and that is a design decision, not a training problem. Fewer things on screen, the important buttons where the eye already goes, and the steps in the order your team actually does them. Before handover we run it on real work together, and I leave written instructions they can go back to.
I do not know what I need yet. Where do I start?
By telling me what today looks like. What people do, where it goes wrong, who has to chase whom. You do not need answers before you email me. Some of what you describe will not need software at all, and I will tell you that rather than quietly building it.
Can we add to it later?
Yes, and I build expecting that you will. I keep the pieces separate so a new one can be added without disturbing what already works. There is usually no need to build everything at once.
I run a business in Thailand but I am not Thai. Does that complicate things?
Not really, and in some ways it helps. I work in English and Thai, so I can build you an owner's view in English and a staff view in Thai from the same system, and you are not relying on someone to translate between you and your own software. I have built sites and systems that run in more than one language before, including one serving Thai and cross-border customers at the same time.
Wondering what a system like this costs? Here is what actually moves the number.
Describe a normal week and we can work out where to start
No specification needed. Just tell me who does what, and which part goes wrong most often. That is usually enough for me to see the shape of it.