01 What I build
When the work does not fit on one screen
Some jobs are simply a website. Others need an app, a server, a payment service or a device in the field to work together. I build as much of that system as the job actually needs.
Websites & content platforms
I build marketing sites, product pages and content platforms. I care as much about how quickly they open and how independently your team can update them as how they look on a phone.
Marketing site · CMS · SEO
IoT & connected devices
I treat the firmware, the service receiving its data and the control panel as one system. Being able to find a problem in the field is as much a part of the work as getting the system running.
Telemetry · Remote control · OTA updates
iOS & Android apps
I take iOS and Android apps from the first working screen to the store. Weak connections, notifications and the work of shipping another release are considered early, not left until launch.
iOS · Android · Store release
Service integrations
I connect payment, shipping, accounting and CRM services to your software. That includes what happens when a service stops responding, how the error becomes visible and how your data is kept intact.
API · Payment / CRM · Webhooks
02 Working together
There is no account manager in between
From the first call to the final handover, you work directly with me. The person understanding the need, making the technical decisions and writing the code does not change.
-
We start with the problem
First call · 60 minutes
Before discussing what software you want, I want to understand what you are trying to solve. If an existing product meets the need, I will say so instead of trying to sell you a custom build.
-
I put the decisions in writing
Scope · Schedule · Budget
I put what will be built, what will wait, the schedule and the budget in one document. If something changes later, we look at the effect together before I change the code.
-
I show you the working thing
Two-week cycles
I split the project into small, working pieces. Each cycle ends with a build you can open and try, so a status report is not your only evidence of progress.
-
You keep the keys
Handover · Documentation · Care
The repository, servers, domains and store accounts are set up in your name or transferred to you. You are not locked into me after launch; if you want, I can stay on for maintenance and further work.
03 During the project
You do not have to take my word for the progress
Your project board shows what is finished, what I am working on, what comes next and the latest working build. If something slips, the reason and the revised date appear there too.
-
Where we are today
I update the board as the work changes. You do not have to wait for a scheduled meeting to find out where things stand.
-
A build you can try
I share new builds with a link as they become ready. You can judge the working product, not just a description of it.
-
A schedule that shows changes
When a date changes, I add the new date and the reason to the board. I do not save bad news for the end of the month.
The board is included with every project. It is not an add-on.
04 — Technical approach
The first question is: what does this job need?
I do not leave performance for a final check. Data volume, connection quality, maintenance cost and the way your team will use the system shape the technical choices from the start. These are tools I work with, not a checklist for every project.
05 Contact
Tell me what you want to do. You do not need to know how to build it.
It may be a local business's first website or a new piece of a large company's existing system. A few sentences are enough. If the work is outside my field or an existing product is the better answer, I will tell you that too.
The first call is free. I will not turn it into a sales presentation.