Systems & Automation
Custom web systems to get your business off spreadsheets.
Customers, orders, schedules and finances in one place, accessed from the browser, the way your business works. Before writing any code, I understand the process with you.
Which of these sounds like you?
The same information gets typed two or three times.
The order comes in on WhatsApp, goes into a spreadsheet and then to finance. Every copy is a chance for errors and a chunk of someone's day.
What I do
I build a system where information goes in once and shows up wherever it's needed: the order, the inventory and finance.
I only know how the business is doing when someone builds a report.
To know how much you sold, what's late or who hasn't paid, someone has to stop what they're doing and merge spreadsheets.
What I do
The system shows those numbers on a dashboard, updated while the team works.
The tools I use don't talk to each other.
Each tool handles one part, but none of them talks to the others, and your team becomes the bridge between them.
What I do
I connect the system to what you already use, when the tool allows it, so data moves from one place to another on its own.
Is a custom system what you need?
It makes sense if…
- Your team wastes time copying information from one place to another.
- The way your business works doesn't fit off-the-shelf software.
- You depend on spreadsheets only one person understands.
- You pay for several tools and still need workarounds.
It might not be the right fit if…
- The process still changes every week. It's worth letting it settle before turning it into a system.
- Off-the-shelf software already handles your case well. Then buying it is cheaper.
- The problem is a one-off. Sometimes a simple automation solves it without a whole system.
If you recognized yourself in the “might not” list, I'll tell you right away in our first chat and point you to what makes more sense.
What comes with every system I build
The process understood before the code
Before coding, I map with you how the work happens today: who does what, where information comes in and where it gets stuck. The system is built from that map.
- Process mapped with you
- Screens designed before code
- Scope approved before we start
Everyone sees what they need
Role-based access: sales sees their own orders, finance sees the cash flow and you see everything. Depending on the system, every change is also logged with who made it and when.
- Role-based access
- Change history, when it makes sense
- Works on desktop and mobile
Numbers without building reports
Dashboards with what matters to your day: sales, open orders, receivables. Updated on their own, with no spreadsheet in between.
- Dashboard with today's numbers
- Reports without spreadsheets
- Export when you need it
Connected to what you already use
When the tool allows it, the system connects to what you already use, like payments or invoicing. Before promising, I confirm the connection is possible. More elaborate automated flows fall under the automation service, contracted separately.
- Integrations confirmed first
- Payments and invoicing
- Automations separately, if needed
Truly yours
The code, the documentation and the logins stay with your business. If you ever want to switch vendors, another team can carry on without rebuilding the system. And if you'd rather stay with me, maintenance is optional: the person who built it takes care of it.
- Your code and documentation
- 30 days of bug fixes included
- Optional maintenance with the builder
How it works
- 1
Conversation
You tell me which process is stuck and how it works today. I come out of it knowing whether it calls for a system, an automation or off-the-shelf software.
- 2
Map and proposal
I map the process with you and send the scope, timeline and price before we start. What we agree on doesn't change without us talking first.
- 3
Screens
I design the main screens before the code, so you can see how the system will work and approve the path for each task.
- 4
Development in parts
I build the system in parts, and you use each one working through a preview link instead of waiting for everything to be ready.
- 5
Rollout
I launch the system, help bring over the data from your spreadsheets and show the team how to use it.
- 6
After launch
For the first 30 days, fixing any bug is already included. After that, as the business grows, the system can gain new parts and, if you want, I keep handling the maintenance.
Questions about custom systems
- How much does a custom system cost?
- It depends on the number of screens, access roles and integrations. After a quick chat, I send the price before we start. If you ask for something new along the way, we talk about the adjustment before I do it.
- How long does it take?
- It depends on the size. A system focused on one process is ready well before one with many parts. The timeline comes in the proposal, and we can start with the essentials and grow in parts.
- Isn't off-the-shelf software better?
- Sometimes it is. If ready-made software handles your case well, I'll tell you, and you save money. Custom makes sense when the way you work is part of what sets your business apart, or when the workarounds on top of off-the-shelf tools already cost too much.
- Is the system mine?
- Yes. The code, the documentation and the logins are handed over to your business, and another team can carry on with the system if you ever want to switch vendors. Maintenance with me is optional: the person who built it knows it best.
- Does it work on mobile?
- Yes. The system runs in the browser, so your team can use it from a computer or a phone, with nothing to install.
- What about the data that's in spreadsheets today?
- It goes into the system. Before the switch, we organize the spreadsheets together so nothing gets lost along the way.
Goes well with
Let's talk
Tell me what you need.
No commitment, no sales script, no surprise calls. You explain the idea, I tell you how I'd build it — and if it makes sense for both of us, we move forward.