Clarify first, then quote, then build.

Eight stations in a fixed order.

It becomes binding when the contract is signed. Everything before that is for clarifying.

1. 01First contact
2. 02Analysis
3. 03Requirements
4. 04Quote
5. 05Contract
6. 06SpecificationFrom here we build
7. 07Sprints
8. 08Launch

1. Before the contract

   Here we work out what you need and what it costs.

2. 01

   First contact

   You write to us or call and tell us what you have in mind. We listen and tell you honestly whether we’re the right people for it. If we aren’t, we say that too.

   zeasy briefing --output

   • A meeting date
   • a first take on whether it fits
   • no obligation

3. 02

   Requirements analysis

   We go through goals, users, workflows and APIs until it’s clear what the system has to do. We ask most of the questions. You don’t need to know everything up front.

   zeasy analysis --output

   • Goals and user groups
   • the most important workflows
   • open questions on your side

4. 03

   Requirements document

   The requirements document comes from you. It describes what you need: features, data, deadlines and constraints. How it gets built is not part of it. The analysis gives you the material for it.

   zeasy requirements --output

   • Features from your point of view
   • deadlines and constraints
   • the basis for our quote

5. 04

   Quote

   Based on your requirements document, we write a quote: which services, what they cost, when they’ll be done and what is not included.

   zeasy quote --output

   • Services and their scope
   • price
   • schedule
   • what is not included

   05

   Contract

   Work starts with the signature. The contract is based on the quote and your requirements document. From here, what was agreed applies, and we plan the start.

   zeasy contract --output

   • Signed contract
   • start date
   • a fixed point of contact

6. Four documents, one order.

   Each builds on the one before. Each says who writes it.

   You

   Requirements document

   What you need, from your point of view.

   We

   Quote

   Scope, price and schedule.

   Both

   Contract

   What applies, and from when.

   We

   Specification

   How it gets built, with acceptance criteria.

7. After the contract

   This is where we build. You decide at the points marked further down.

8. 06

   Specification

   The requirements document becomes the specification, the technical version. It covers the data model, APIs, user interfaces and acceptance criteria. You review it and approve it. Only then do we build on it.

   zeasy spec --output

   • Data model and APIs
   • acceptance criteria per feature
   • your approval

9. 07

   Sprints

   We build in one-week sprints. Each one starts with joint planning and ends with a demo you see. In the retro we note what we’ll do differently. Whatever doesn’t fit in the demo moves into the next sprint.

   zeasy sprint --output

   • Weekly demo with you
   • current build on a test system
   • list of changes per sprint

10. 08

    Launch and operations

    Once the acceptance criteria are met, the system goes live: with domain, hosting, tracking and the GDPR basics. After that we keep looking after it if you want us to.

    zeasy launch --output

    • Sign-off against the specification
    • go-live with domain and hosting
    • maintenance if you want it