Process — five phases

Five phases, no surprises.

Every engagement follows the same route, from a website to a platform. So on day one you know what happens on day forty, what it costs and when it goes live.

  • 5phases, for every project
  • 1 weekto scope, price and date
  • 1×a week something to see
  • < 1 dayreply to every question

The five phases

From first call to growth

  1. Discovery

    1 week

    We map goals, users, systems and risks. You get a scope, a fixed price, a date and a technical plan.

    What you get

    • Scope document
    • Technical plan
    • Price & schedule

    How we work together

    • 90-minute kickoff
    • Stakeholder interviews

    Your roleYou provide system access and one decision-maker.

  2. Design

    1–3 weeks

    Structure, flows and visual design in a design system. You see a clickable prototype every week and decide based on something real.

    What you get

    • Wireflows
    • Design system
    • Clickable prototype

    How we work together

    • Weekly 45-minute review

    Your roleYou give feedback within two business days.

  3. Build

    2–10 weeks

    Development in two-week sprints, with tests, a preview environment and a deploy a day. Content and integrations run in parallel.

    What you get

    • Preview environment
    • Sprint demos
    • Test report

    How we work together

    • Demo at the end of every sprint
    • Daily progress in a shared channel

    Your roleYou deliver content and test the previews.

  4. Launch

    1 week

    Performance, accessibility, SEO and security are measured before go-live. Migration without losing rankings, go-live on a Tuesday.

    What you get

    • Lighthouse report
    • Accessibility check
    • Go-live checklist

    How we work together

    • Go-live on a Tuesday
    • Handover and training

    Your roleYou approve the checklist and switch DNS (or we do).

  5. Grow

    ongoing

    Measure, improve, extend. With Care or a Continuous team the product keeps getting better, on a roadmap you set.

    What you get

    • Monthly report
    • Roadmap
    • SLA

    How we work together

    • Quarterly roadmap session

    Your roleYou pick the priorities for the next quarter.

AI

AI-native, with a senior at the wheel

In every phase we use AI for the work that can go faster, and a human for the work that requires judgment.

  1. AI doesSummarizing documentation, competitor analysis, first architecture variants

    Discovery

    A human decidesConversations, decisions, scope and price

  2. AI doesVariants, copy suggestions, accessibility checks

    Design

    A human decidesConcept, hierarchy, every final screen

  3. AI doesBoilerplate, tests, migrations, documentation

    Build

    A human decidesArchitecture, code review, every line that ships

  4. AI doesChecklists, performance analysis, redirect mapping

    Launch

    A human decidesGo/no-go, handover, training

  5. AI doesReports, anomaly detection, content variants

    Grow

    A human decidesRoadmap, priorities, strategy

The deal

What we agree

A project works when both sides know what to expect. This is our side, and this is what we ask of you.

What we promise

  • Fixed priceAgreed in writing up front. Overrun is our risk.
  • Fixed dateA delivery date we meet, or we tell you well in advance with a reason.
  • Reply < 1 business dayEvery question gets an answer within one business day, during and after the project.
  • Lighthouse ≥ 90Every delivery is measured on performance, accessibility, best practices and SEO.
  • WCAG 2.2 AAAccessibility is a design requirement, not an afterthought.
  • Everything yoursCode, design, domains, data and accounts are in your name from day one.
  • 30 days of aftercareAfter go-live we fix anything that isn’t right for a month, no discussion.
  • Honest adviceIf we’re not the right party, we say so and refer you on.

What we ask of you

  1. One decision-makerOne person on your side who makes the calls. That keeps the pace high.
  2. Feedback within two business daysEvery review has a deadline. That’s how a fixed date stays a fixed date.
  3. Access to systemsAPI keys, test environments and accounts in the first week, so integrations don’t wait.
  4. Content on timeCopy, images and product data per the content plan, or let us create them.

How we work together and what it costs

Questions

Questions about how we work

Tap a question for the answer. Yours isn’t there? Type it below and I’ll put it in the contact form.

Replies within one working day

info@rabzi.nl
RABZIReplies within one working day

How long does an average project take?

A website 3 to 6 weeks, an e-commerce store 6 to 12, an app or platform 8 to 20 weeks. Discovery always takes one week; after that you know exactly how long your project takes.

Other questions

How long does an average project take?
A website 3 to 6 weeks, an e-commerce store 6 to 12, an app or platform 8 to 20 weeks. Discovery always takes one week; after that you know exactly how long your project takes.
What happens if the scope changes during the project?
We never quietly add hours to the invoice. You get a short note with the impact on price and date, and you decide. Small things we simply fix.
Can I follow along in between?
Always. From the first sprint there is a preview environment and every sprint ends with a demo. You never see the result only at the end.
Do you work with contracts and a data processing agreement?
Yes. An engagement letter with scope, price and date, our terms and conditions and, when we process personal data, a processing agreement. All in Dutch or English.
What if I want to bring in someone else after delivery?
You always can. Code, documentation and access are yours; we do a proper handover. Our terms say so explicitly.

Ready for phase one?

A one-week Discovery Sprint gives you a scope, a fixed price and a date. Credited when we continue together.

info@rabzi.nl

Intro call with RABZI30 minutes · no strings

Pick a moment that suits you

Request this momentMon 23 Nov · 14:00

You’ll get a confirmation within one business day.