You will get a working MVP of your product idea, live in weeks not months
Project details
The most expensive mistake founders make is building for six months before anyone uses it. I build the smallest version that a real customer can actually use, and get it live.
Not a slide deck, not a Figma file. A working product on your own domain, with accounts, real data and the one flow that proves people want this. Next.js, TypeScript and Supabase, running in your accounts, so you own everything from day one and are never locked to me.
Every week you get something clickable. That is deliberate. Ideas change once you see them working, and changing your mind in week two is cheap while changing it in month five is not.
I also say no. If a feature will not help you learn anything, it goes on the later list instead of into the first version.
I run my own companies and have launched things that worked and things that did not. You get that judgement as part of the build, not just the code.
Not a slide deck, not a Figma file. A working product on your own domain, with accounts, real data and the one flow that proves people want this. Next.js, TypeScript and Supabase, running in your accounts, so you own everything from day one and are never locked to me.
Every week you get something clickable. That is deliberate. Ideas change once you see them working, and changing your mind in week two is cheap while changing it in month five is not.
I also say no. If a feature will not help you learn anything, it goes on the later list instead of into the first version.
I run my own companies and have launched things that worked and things that did not. You get that judgement as part of the build, not just the code.
Programming Languages
PHP, JavaScript, TypeScriptCoding Expertise
Performance Optimization, SecurityWhat's included
| Service Tiers |
Starter
$1,500
|
Standard
$3,800
|
Advanced
$7,200
|
|---|---|---|---|
| Delivery Time | 10 days | 22 days | 35 days |
Number of Revisions | 1 | 2 | 3 |
Design Customization | - | - | - |
Content Upload | - | - | - |
Responsive Design | |||
Source Code |
Frequently asked questions
About Tom
Custom Software Engineer | CRM, AI Agents, Automation | Next.js
Mauren, Liechtenstein - 7:23 pm local time
WHAT I BUILD
- Custom CRM and sales systems: pipelines, activity tracking, email sequences, automations, reporting
- Internal tools and back-office systems that replace the spreadsheet everyone is afraid to touch
- Client and member portals with logins, document upload and role-based access
- AI voice agents that answer and place calls, and AI chat agents that qualify website visitors
- Workflow automation and API integrations between the systems you already run
- SaaS MVPs for founders who need something users can actually use
WHY CLIENTS HIRE ME
I have built and I operate a complete sales CRM: pipelines, telephony, email sequences, automations, AI agents, multi-tenant permissions. Most of what your project will run into, I have already solved once at my own cost - deliverability, call recording, row-level security, data migration, background jobs. I am not learning it on your budget.
I work solo and direct. You talk to the person writing the code; there is no account manager relaying requirements.
HOW I WORK
1. A short call to map the workflow and the edge cases
2. A clickable prototype before development starts, so we argue about the design and not about the invoice
3. Weekly increments you can click through yourself
4. Handover: source code, documentation, deployment, walkthrough video
STACK
TypeScript, Next.js, React, Node.js, PostgreSQL,
Based in Liechtenstein, working with clients across Europe and the US. Native German, fluent English.
Send me the workflow you want fixed. You get an honest scope, a fixed price, and a straight answer if I am the wrong person for the job.
Steps for completing your project
After purchasing the project, send requirements so Tom can start the project.
Delivery time starts when Tom receives requirements from you.
Tom works on your project following the steps below.
Revisions may occur after the delivery date.
Cut the idea down to one flow
Most first versions fail because they try to do everything. We pick the single path that proves people want this, and everything else goes on a later list.
Build in weekly slices
Every week you get something you can click, on your own accounts. That way you steer while it is still cheap to change, instead of seeing it all at the end.