Services · Process

Technical software
that actually gets used.

Dense logic, persistent data, precise interfaces and deliverables the client can take into the physical world. And a clear process, told step by step.

What I build

Products, not templates.

Calculation apps

Engineering, cost, sizing or energy calculators. A tested math engine and real-time results.

Quoting tools

Quoters with rates, discounts, VAT and export to PDF/XLSX. Your sales rep closes deals from their phone.

Product configurators

The client picks sizes, materials and finishes; the app computes the price and sends the order to the ERP or by email.

Technical 3D viewers

Parametric models in the browser with Three.js: rotation, layers, measurements and export to OBJ/DXF.

Dashboards and back-office

Operations panels: users, metrics, billing, OAuth auth, plans and permissions. Supabase + RLS from day one.

PWA + continuous deployment

Installable apps, offline mode, automatic deployment on Cloudflare or Vercel, your own domain and careful technical SEO.

How I work

A weekly rhythm, demos every Friday.

No agencies in between. No months of silence. Every week there's something to touch and a decision to make.

Phase 0130–45 min

Initial conversation

You tell me the problem and what you've tried. We come out with a written mini-diagnosis and a first scope estimate.

DeliverableOne-page document with goal, risks and next step.
Phase 023–5 days

Short spec and proposal

I turn the conversation into a brief technical document: what gets built, what doesn't, how success is measured, in how many iterations and at what price.

DeliverableSpec + fixed quote by phases.
Phase 03Every Friday

Weekly iterations with a demo

Every Monday we prioritise the week together. The code is in your GitHub from day one. No surprises at the end.

DeliverableApp deployed to staging every week + changelog.
Phase 04Production

Launch and maintenance

Deploy to production, your own domain, live metrics. Afterwards: monthly hours, enhancements, or you take the code and run it yourself.

DeliverableTechnical handover, runbook and connected metrics.
Phase 0130–45 min

Initial conversation

You tell me the problem and what you've tried. We come out with a written mini-diagnosis and a first scope estimate.

Phase 023–5 days

Short spec and proposal

I turn the conversation into a brief technical document: what gets built, what doesn't, how success is measured and at what price.

Phase 03Every Friday

Weekly iterations with a demo

Every Monday we prioritise together. The code is in your GitHub from day one. No surprises at the end.

Phase 04Production

Launch and maintenance

Deploy to production, your own domain and live metrics. Afterwards, enhancements or you take the code.

Why hire me

Criteria almost nobody applies.

01

I talk to whoever uses the tool

Before writing code I reach out to the real users to understand what holds them back. That's how DomesLab's axial cut was born: from a conversation, not an assumption.

02

I review what I deliver

I test the product, leave it truly working and documented — not a half-finished demo.

03

I build with the future in mind

I separate the product logic so it can be extended or maintained without rebuilding it.

04

Continuous, auditable delivery

Lint, typecheck and tests on every PR. Automatic deployment on every push to main. Every change, reversible.

Frequently asked questions

What people usually ask.

01

What kind of software do you build?

Custom technical software: engineering calculators, quoting tools, product configurators, in-browser 3D viewers and operations dashboards. Tested logic and persistent data, not templates. If your team keeps redoing a calculation in Excel, or your clients ask for something the market doesn't offer, that's exactly what I build.

02

Do you work directly with the client or through an agency?

Directly, no agencies or middlemen. You talk to the person writing the code. Every Monday we prioritise what's next together and every Friday there's a demo you can touch; no months of silence and no quotes that balloon along the way.

03

When do I see the first result?

The first technical spec and the fixed quote arrive within 3–5 days of the initial conversation. From there I ship a deployed version every week, with a demo on Fridays. You see real progress from week one, not a single delivery at the end of the project.

04

Who owns the code when we're done?

You do, from day one. The code lives in your GitHub repository throughout the project. At the close you get a technical handover with a runbook and connected metrics, so you can audit it, extend it with someone else or maintain it yourself, without depending on me.

05

What happens after launch?

You choose: a monthly maintenance plan (hosting kept up to date, backups and changes), enhancements by the hour, or you take the code and run it yourself. There's no mandatory lock-in. The goal is for the tool to keep working, whoever maintains it.

06

How is this different from a template or a no-code tool?

A template gives you a shape; I solve your specific logic: the calculation, the business rules, the exports and the integration with your ERP or your email. I keep that logic separate from the rest so it can be extended or maintained without rebuilding the whole product.

Next step

Let's build your tool.

Tell me what your team or your clients need. In under 48 hours I'll reply with a diagnosis, a scope estimate and the next decision.

Start your project