S.00How I work

How a project with me runs

The schema shows how a brief becomes a product in production. Below it is the same path step by step, with a note on what I do and what the AI agents do.

How I build software Diagram of the process: brief, my design and architecture, four parts (backend, web, mobile, AI and data) built in parallel with agents, my review and tests, deploy, production, and feedback from production into the next round. BRIEF BACKEND WEB MOBILE AI AND DATA DEPLOY PRODUCTION NEXT ITERATION DESIGN ANDARCHITECTURE REVIEW ANDTESTS How I build software Diagram of the process: brief, my design and architecture, four parts (backend, web, mobile, AI and data) built in parallel with agents, my review and tests, deploy, production, and feedback from production into the next round. BRIEF DESIGN ANDARCHITECTURE BACKEND WEB MOBILE AI ANDDATA REVIEW ANDTESTS DEPLOY PRODUCTION NEXT ITERATION
  • I decide and check
  • Agents build in parallel
  • Feedback from production

S.01Steps

Six steps from brief to production

  1. 01 Me

    Brief

    In a meeting or in your inquiry I find out what the system should solve, for whom and what the priority is. That becomes the brief I work from.

  2. 02 Me

    Design and architecture

    I design the data model, split the system into parts and choose the technology. For each part I write a brief for the agents, so they know exactly what to build and how the pieces fit together.

  3. 03 AI agents

    Parallel lines

    Agents build the backend, the web, the mobile app and the AI with data at the same time, each in its own line, from my brief. Parts wait for each other only where one really depends on the other, such as an app screen that needs a finished API.

  4. 04 Me

    Review and tests

    I go through and test everything the agents produce. What doesn't pass goes back into the line. Nothing gets deployed that I haven't seen.

  5. 05 Me

    Deploy

    I do the deploy to production. I decide what goes out and when, and I keep access and client data under my control.

  6. 06 Me

    Operations and next iterations

    A system in production gives feedback: what people use, where it hurts, what is missing. I plan the next round from that, and it loops back to the design.

S.02My part

Four things I keep for myself

  • Design and architecture

    The data model, the split of the system into parts, the choice of technology and the briefs for the agents. Everything else follows from these decisions, so I make them myself.

  • Review and tests

    I read and test everything the agents produce. An agent delivers fast, but I answer for the result, so nothing moves on without a check.

  • Security and client data

    I decide who has access to the system, which data may go to an external model and which may not, and I do the production deploys.

  • Communication with the client

    I handle the brief, the priorities and the scope decisions directly. The client talks to the person who knows what is going on in the system.

S.03Team

When a team joins

A team is not part of every project. When it joins, it is people from the IDEATECH network, the company where I work as CTO.

  • Design and UX
  • More developers
  • Testing and support
  • Project management

  • Scope or deadline

    The project is bigger than what one person with agents can finish by the deadline you need.

  • Operations after launch

    Support and SLA can't depend on one person, so a team joins for operations.

I lead smaller projects on my own and deliver bigger ones as a contract through IDEATECH.

S.04Pace

What has been built this way

Three things that show how long this approach takes and how much gets built in that time.

01

IdeaWood

A web app, a mobile app and maps on one shared backend, in production, roughly four months since development of the apps started (July 2026)

02

Teramex

A platform for working with documents, built solo, in pilot operation

03

Faktury

My own replacement for Fakturoid in three days

Done in that time

  • Import from Fakturoid, including archived PDFs
  • Secure sign-in for a single user with a two-factor code
  • Contacts loaded from ARES, with VAT payer checks
  • Invoices with a numbering series, change history, credit notes and duplication
  • PDF with a QR payment code, ISDOC export and a public web view of the invoice
  • Emails with invoices, reminders and thank-you messages
  • Backups to S3 with verified restore
  • Running in production
  • Matching payments to invoices from the Fio bank
  • Ongoing calculation of taxes and contributions
  • Documents for the tax return and the overviews for the social security and health insurance offices
  • An API for connecting other tools

S.05Working together

How the collaboration runs

  1. 01

    Intro call

    We go through what you want to solve, for whom and what the current state looks like. I can tell whether I can help, and you can tell how we will talk to each other.

    You get: notes from the call and the next steps

    30 to 60 minutes
  2. 02

    Deeper brief

    We go through the assignment in detail: goals, users, links to existing systems, data and constraints. Open questions get written down, not guessed at.

    You get: a written brief and the open questions

    one to two weeks
  3. 03

    Proposal

    From the brief I prepare a proposed solution. It includes scope, deadline and price, so you know what you get, by when and on what terms.

    You get: a proposal with architecture, scope, deadline and price

    within a week of the brief
  4. 04

    Development and deploy

    Agents build in parallel from my design, and I check and test everything. I do the deploy to production.

    You get: a running version on a test environment, then the production deploy

    depends on scope, the first running version on a test environment usually within four weeks
  5. 05

    SLA

    Operations, monitoring and support after launch run under a contract through IDEATECH, so they don't depend on one person.

    You get: a contract for operations, monitoring and support

    ongoing, under the contract

S.06Questions

What people ask

Who is responsible for the project when AI agents work on it?

I am. The agents build from my design, but I do the review, the tests, the security and the production deploy myself.

How do I get a price?

The price is part of the proposal I prepare after the deeper brief, together with scope and deadline. I don't quote it up front because it depends on what the brief turns up.

What if the project outgrows one person?

A team from the IDEATECH network joins: design, more developers, testing and project management. I lead smaller projects on my own and deliver bigger ones as a contract through IDEATECH.

Where does my company's data go?

I decide who gets access to the system, which data may go to an external model and which may not. I do the production deploys, so access and client data stay under my control.

Have a project that needs a whole system?

Describe what you need in an inquiry and I'll get back to you with the next steps.

Write to me