From question to working software
- 01
01
Discovery & analysis
We do not start with a feature list, but with your business.
First we map out which user experiences which problem, how the current process runs and which result matters: more relevant enquiries, less time on admin, faster service or better information for customers. Existing systems and edge cases go on the table too.
After this analysis it is clear whether you need a custom website, a web application, an integration, or actually a simpler solution. If an off-the-shelf package is enough, I will say so honestly.
What you get: A clear proposal with scope, timeline and investment.
- 02
02
Building in short steps
You respond to working software, not to a theoretical specification.
Not every wish needs to be built before launch. Parts that prove the core process or remove a real risk come first; ideas without direct value stay on a transparent follow-up list.
For content-rich websites I test information architecture and sample pages early. For applications we look at roles, the data model and the main workflow first. You always see a working preview and steer directly, before expensive assumptions get locked in.
What you get: Visible progress and a working preview, every week.
- 03
03
Launch & beyond
Going live is a controlled step, not a last-minute rush.
Before launch I check content, forms, permissions, error scenarios, redirects and metadata. Where relevant I set up analytics, monitoring and backups.
After going live there is a short evaluation: are enquiries coming in properly and does the process work as intended? Small improvements ship fast; larger extensions are re-prioritised on value and risk. That keeps further development a business decision, not an endless wish list.
What you get: A controlled launch and a partner for what comes after.
One engineer, AI-accelerated
Why this moves so fast
Agency pace without agency overhead is not a marketing promise, but the direct result of how I work.
At a traditional agency your project passes through sales, project management, design and development. Every handover costs time and detail. Here, one senior engineer does the analysis, the design and the code. Nothing gets lost along the way.
I also use AI where it demonstrably accelerates: writing and reviewing code, testing, documentation and content structure. The gain is not lower quality, but fewer lost hours. You see that speed back in the timeline and in the price.
And I bring the same experience to your processes. What I automate for my own work, I automate for yours: from smart intake to document processing with human review.
No handovers
Analysis, design and code by the same person. Decisions explained in plain language.
AI where it accelerates
AI tooling for building, testing and documenting. Critical logic stays plain, verifiable software.
Enterprise foundation
Seven years of API management and event streaming at Eneco, applied to SMB solutions.
Why custom?
When custom pays off
A custom website or application is not a goal in itself. The investment pays off when your processes, integrations or growth plans do not fit neatly into a standard template.
A WordPress theme or page builder can be fine for a simple informational site. But as soon as customers need to log in, data has to come from multiple systems or a unique intake makes the difference, tension builds between your process and the limits of the platform.
Custom mainly means control: over performance, findability, security and further development. You pay for a foundation that fits your organisation, not for dozens of features you never use. If the website later grows into a client portal or web application, it can happen on the same base.
Less technical baggage
Only the code and functionality you actually need, without a pile of plugins affecting each other.
Exactly your process
Forms, roles, calculations and workflows follow the way your business works, not the other way around.
Ready to grow
New services, languages, integrations and portal features are added in a controlled way.
Who it is for
Who I build for
Organisations with a serious commercial or operational question. Not the cheapest brochure website, but software that demonstrably improves work.
Technical & installation
Clear propositions, quote intakes, service flows, calculators and integrations with planning or CRM.
Logistics & manufacturing
Order portals, status information, document flows, operational dashboards and system integrations.
SaaS & growing SMB
MVPs, client portals, payments, multi-user software and an architecture that can grow along.
Investment and return
Judging the investment
The cheapest delivery price is rarely the best comparison. Look at revenue, saved time, risk and the cost of change over several years.
For a commercial website the business case starts with the value of a good enquiry. If clear service pages, cases and a better intake bring in a few extra qualified conversations per month, that outweighs a small difference in build cost.
For portals, dashboards and integrations the value sits in recurring work. Calculate how many hours your team spends each week on retyping data, finding documents, answering status questions or fixing errors. One reliable source of truth or clear self-service already saves structural time and frustration.
Custom work requires a larger initial investment than a template, but becomes cheaper when generic plugins, manual workarounds and recurring repairs disappear. If custom does not make sense for your situation, you will hear that in the first conversation.
Commercial value
Quality of enquiries, conversion to conversations and the contribution of content and tools to your sales process.
Operational savings
Making hours, handovers, errors and customer questions per month visible before budgeting automation.
Total cost of ownership
Not just the build price, but also licences, maintenance, cost of change and transferability.