Process
How we'll work together, from first call to long after launch.
Simple, predictable and transparent, so you always know where the project stands and what it costs. The same four steps for a two-day fix and a two-year engagement.
Start here
Four steps
From first call to launch
Intro call
A free 30-minute call where you tell me about your project, goals and constraints. I ask a lot of questions and tell you honestly whether I'm the right fit.
Proposal & estimate
You get a short written proposal: scope, approach, timeline and price. Fixed price for well-defined projects, hourly or retainer for ongoing work.
Build in the open
Short iterations, working software early, and a weekly update you can actually read. You see progress and can change course before it gets expensive.
Launch & support
I handle deployment, hand over clean documentation, and stick around for support and further development if you want me to.
Engagement models
Fixed price, retainer or hourly
Which one we use depends on how well the work can be defined up front. Rates are in the proposal, never a surprise.
- Fixed priceWell-defined projects with a clear scope.
- You get a written scope, timeline and price up front. Changes are agreed in writing before they cost anything. Good for MVPs, calculators, portals and modernisation projects with a known end state.
- RetainerOngoing development, 20-40 hours a week for six months or more.
- Reserved weekly hours, billed monthly. You get continuity, predictable capacity and a developer who knows your product. This is how most of my long engagements run, and the shape I prefer.
- HourlySmaller tasks, audits and work that is hard to scope.
- Billed monthly for the hours used, with a written log. Often the first step before a retainer, or the right fit for a two-day fix.
What to expect
What you get every week, not just at launch
A weekly written update
What shipped, what is next, what I need from you, and anything that changed. Short enough to read, complete enough to forward.
Working software early
Something you can click within the first weeks, then steady iterations. You see progress instead of waiting for a reveal.
Honest answers
If I think there is a better way, I will say so. If I am not the right fit, I will say that on the first call. Realistic estimates and early warnings, not surprises.
Your code in your repository
From day one. Documented, reviewed and deployable by someone who is not me. Long tenure is continuity, not dependency.
Async first, EU timezone
Written communication by default, calls when they help. Full overlap with Europe and the UK, 3-6 hours with the US East and Central timezones.
Support after launch
Deployment, handover and documentation are part of the work. If you want me to stay for support and further development, that is the usual outcome.
FAQ
Practical questions
- How quickly do you reply and start?
- I usually reply within a day. If my availability status says available, I can typically start within one to two weeks of agreeing a proposal.
- Do you publish rates?
- No. Rates depend on the scope and engagement model and live in the proposal. You will always know the price before any work starts.
- What do I need to prepare for the intro call?
- Nothing formal. Come with what you are building, roughly when it needs to exist and what a great result looks like. I will ask the rest.
- How do you invoice?
- From my Danish company, Pekkel (CVR DK-37106666), in EUR, DKK or USD. Monthly for retainers and hourly work, milestone-based for fixed-price projects.
- Can we sign an NDA and a contract first?
- Yes. I am happy to sign your NDA before we go into detail, and I work under your contract or a short standard agreement of mine.
- What if the project changes direction?
- That is expected. Short iterations exist so we can change course while it is cheap. We adjust the scope in writing and carry on.
Contact
Step one is a free 30-minute call
Tell me what you are building, roughly when, and what a great result looks like. I usually reply within a day.