How it works

    From conversation to proof to running software.

    The line, station by station: what humans decide, what agents build, and the proof every requirement carries when it leaves the line. Then what it means for an agency and its clients.

    How the factory works

    Every requirement leaves the line with its proof attached.

    A factory is a sequence you can write down, repeat and check. Product Printer runs that sequence for software: humans decide what to build, coding agents build it, and every acceptance criterion is bound to a real test run before anything is called done.

    1. 01

      Discovery

      The brief, constraints and decisions on record.

      Conversation, not a form

    2. 02

      Requirements

      Acceptance criteria written before a line of code.

      One criterion, one check

    3. 03

      Open questions

      Nothing is built on an assumption.

      Asked, answered, closed

    4. 04

      Solution + UI

      Screens and data model, reviewed.

      Design decided before code

    5. 05

      Worksteps

      Sized work orders, one agent each.

      Agents build, not guess

    6. 06

      Proof

      A real test run bound to each acceptance criterion.

      Proof, not a checkbox

      The differentiator
    7. 07

      Running software

      Released, versioned, owned by you.

      Yours from day one

    After launch the line loops: the client starts a change from their own space (AI-assisted), the agency approves it, agents build it, the proof runs, v1.1 is released.

    For agencies

    Your printer. Your clients. Your revenue.

    Run the printer locally, on your own subscription. Give every client an online experience under your brand. Own it end to end, with the support to make it a great journey for them and a lasting revenue stream for you.

    Your printer · local · your subscription
    Product Printer
    on your machine · your subscription
    Models
    yours, local or by key
    Code
    in your own GitHub organisation
    Costs
    your subscription, your rate
    Local
    The client's space · your brand · your domain
    [client-c].[your-agency].com
    [client-b].[your-agency].com
    [client-a].[your-agency].com/orders
    Orders · order to cashUnder construction
    Worksteps 2 / 4 done
    WS-01Channel intakeProof 3/3
    WS-02ERP syncProof 2/2
    WS-03Invoice on deliveryIn progress
    WS-04Payment remindersQueued
    OQ-02 · waiting for you
    Partial delivery: invoice per shipment or per order?
    Answer →
    Try the running preview →product printer · in the background
    Self-service while it is being built · roles: client · agency team · admin
    After launch · the line loops
    1. Running v1.0
    2. Client requests a change · AI-assisted
    3. Agency approves · scope + price
    4. Agents build
    5. Proof
    6. Released v1.1
    Your monthly line · hosting + change requests + supportHostingChange requestsSupport
    M01M02M03M04M05M06M07M08M09M10M11M12Client A joinsClient B joinsClient C joinsClient D joinsRecurring →
    01

    Print on your own terms.

    Run the printer on your machine with your own subscription. Your models, your costs, and your code stays with you: in your own GitHub organisation, and entirely on your premises with local models.

    02

    Give every client a real online experience.

    Each client gets their own space: requirements, open questions, progress, change requests and documentation, all in one place. They serve themselves while it is being built: answer open questions, review designs, see the proof per criterion, try the preview, request changes.

    03

    Own it end to end.

    Your brand, your domain, your client relationship. Product Printer stays in the background.

    04

    Turn projects into recurring revenue.

    Hosting, change requests and support become a monthly line on your invoice, not a one-off project. After launch your clients start changes themselves, with AI help; you approve scope and price; agents build; proof, then release.

    05

    Supported all the way.

    Supported by the team that runs it daily.

    Proof

    Off the line, still running.

    AvoDev, a Berlin agency, runs its client projects on Product Printer. Several of its client products were delivered on the factory and are still running.

    The reference

    An agency runs its client projects on it.

    The proof

    Every acceptance criterion bound to a real test run before release.

    The ownership

    The generated source and the data belong to the client.

    Join the waiting list Book a walkthrough