Built around your workflow
I sit with your team and watch how the work actually happens. Then I build the dashboard around that. No template-shoehorning. No "configure it yourself" homework left for you.
I build custom dashboards for small businesses still running on Excel, WhatsApp, and five subscriptions nobody opens. One screen for who is doing what, what is due, and where every client stands.
A database. A CRM. A calendar. A reporting tool. Sales_Forecast_FINAL_v7.xlsx. Three people editing offline. Nobody is sure which version is the real one.
Only one person on the team has the full picture in their head. When they are out, the team stalls. The business has a bus factor of one and quietly knows it.
Trello for one workflow. Notion for another. WhatsApp for the urgent stuff. The monthly bill has quietly become real money, and no single screen tells the team what to do today.
Generic tools force your workflow into someone else’s model. You bend. The tool wins. After three months, the team is back in Excel and the subscription is still active.
None of this is a software problem at first. It is a visibility problem. You cannot fix what nobody can see.
Not a SaaS subscription you have to configure. Not a Notion template you have to maintain. A custom tool that matches the way your business already works, built by one engineer who is on the call.
I sit with your team and watch how the work actually happens. Then I build the dashboard around that. No template-shoehorning. No "configure it yourself" homework left for you.
A fancy dashboard nobody opens is wasted money. I design for the least technical person on the team. If they cannot use it on day one, it is not done.
My day job is shipping QA tools for games played by millions. The same standards (documented, tested, built to last) go into every dashboard I deliver.
Fixed-scope pricing quoted up front. No hourly billing during the build. Any bug in the first 30 days after delivery is fixed for free.
Most custom-build conversations end in confusion about scope, cost, and what actually happens when something breaks. This is how I avoid that.
We talk through how your team actually works. I tell you honestly whether software is the right fix, or whether a process change would solve it for free. You leave with a written summary either way. No pitch, no demo script.
If a build makes sense, I write up exactly what gets built, what it costs, and when it ships. You sign once. The price does not move during the build. No surprise invoices.
I share progress as I go. You see what works and call out what is off, while it is still cheap to change. No grand reveal at the end. Documentation written alongside the code, not after.
I train your team, leave clean documentation, and stay on call for the first 30 days. Any bug or issue in that window is fixed for free. No hourly billing for things that should have worked.
I am pre-revenue. There are no testimonials to show yet, and I will not invent any. Instead, here is the demo build I use during the diagnostic call, and the one thing every small business owner I have spoken to has said.
Honest beats polished.
Real working code, fictional client. The kind of build that replaces one Excel file, three WhatsApp threads, and four individual inboxes with a single screen the whole team opens on Monday morning.
Walkthrough video in production. Available as a live demo during the diagnostic call.
We didn’t know this was even a possibility.
A recurring theme across three small business owners I interviewed last month. None were resistant to better tools. None had been shown what better tools could look like for a business like theirs. The gap is not skepticism. The gap is imagination.
I am a QA tools programmer at Guerrilla Games, the studio behind Horizon Zero Dawn. My day job is making sure code that ships to millions of players actually works. That same standard goes into every dashboard I build.
On the side, I build custom internal tools for small businesses still running on Excel. Mostly in the Netherlands, the rest of Europe, and Mexico. The pattern is always the same: one team, one workflow, one screen that finally makes sense.
If you are not sure whether you need software or a better weekly meeting, that is exactly the conversation to have on the free diagnostic call. I will tell you honestly. Some businesses do not need what I build, and I will say so.
Tell me about your workflow. I will tell you whether custom software is the right fix, or whether you can get there with a better weekly meeting and a free template. Either way, you leave with a written summary.