Blueprint · Releases · Care

Approach

Every engagement starts with one process that matters to the business: quoting, scheduling, claims, project delivery or reporting. Wikker works with small and mid-sized businesses of up to 500 people, in English-speaking markets anywhere.

The method differs from most at its first step. A software project usually begins with a long written set of technical and functional requirements, prepared by the client or billed as discovery. We do not ask for one. We interview the owners and the people who do the work, read the records they already keep, and produce a business optimization proposal: what to change in how the work is done, and the software that carries the change.

  1. Conversation
  2. The Wikker Blueprint
  3. Releases
  4. Care

The Wikker Blueprint

A fixed-fee engagement of two to four weeks. A senior Wikker lead interviews the owner, the managers and the people who carry out the process day to day, and reads the records that run it: the spreadsheets, the email trail, the job sheets and the exports from the systems already in place. The findings are played back to the owner and managers as a ranked plan, and the first item on it becomes Release 1.

Length
two to four weeks
Who
a senior Wikker lead; the owner, the managers and the people who do the work
Handed over
the Blueprint: the optimized process, a ranked plan, the Release 1 backlog and the result Release 1 should deliver

Before 9 steps · 4 systems · 3 hand-offs by email

  1. Request arrives by email or phone
  2. Estimator retypes it into a spreadsheet
  3. Prices checked against last year's list
  4. Email to purchasing for supplier costs
  5. Wait for supplier replies
  6. Owner checks the margin
  7. Quote written up in a document
  8. Sent to the customer as a PDF
  9. Signed order rekeyed into accounting

After 4 steps · 1 system · no rekeying

  1. Request captured once, with the customer's details
  2. Price built from current costs and set margins
  3. Owner approves exceptions only
  4. Customer signs online; the order passes to accounting
Illustration of the kind of optimization a Blueprint produces · composite · 2026-11

The Blueprint in Full

Releases

Software arrives in releases of two to four weeks. Each release is fixed in price and scope before it starts, and is invoiced when it runs in your systems. Scope is fixed only for the release in hand. Between releases you re-rank what remains, so the plan follows what the business learns rather than what was guessed at the start. Each release includes the work of getting people to use it: training for the people whose day it changes, and a short acceptance check before it is invoiced.

Length
two to four weeks each
Who
the same senior lead, with the people who will use the release
Asked of you
a scope review before each release and an acceptance check at the end
Handed over
working software in your cloud, and its record on the Release Desk

Release 04

A commercial building-services contractor

Scope

  • work orders opened from customer requests
  • technician schedule by site and skill
  • photos and notes captured on site
  • a weekly summary for the owner
Price
Priced before it started · paid on delivery
Length
3 weeks
Agreed measure
Days from request to technician on site
Today
6.0
Target
3.0
Checked
Six weeks after go-live
Status
Shipped

Reviewed · 2 findings fixed · approved by the client

What a release card looks like · illustration

The Release Desk

The Release Desk is where the method is kept. Every release has one record: its scope, its price, the result agreed before work began, the review it passed, who approved it, and the result measured once it is in use. Your people see the same record we do, along with the running total of the engagement so far. Nothing is approved off the record.

Example
  • R-01 One intake form for every quote request Shipped
  • R-02 Prices built from current supplier costs and set margins Shipped
  • R-03 Online approval and signature for the customer Needs your approval
  • R-04 Signed orders passed to accounting without retyping Planned
Illustration · composite · 2026-11

How Results Are Agreed and Measured

Before a release starts, we agree one measure of what it should change: what is measured, today's figure, the target, and how and when it will be checked. Days from enquiry to quote is a typical measure. Each measure is chosen to depend on what the release controls, or it states plainly what the business must do for the result to follow, since most results depend on people using the software. It is written on the Release Desk when the scope is set and reported a set number of weeks after the release is in use.

It is a goal, not a guarantee, and it does not affect delivery, acceptance or payment.

Week One

Day 1: The senior lead agrees the interview list with the owner and asks for read access to the records that run the process. Days 2-5: Interviews with the owner, the managers and the people at the desk or in the field. Records are read alongside. End of week 1: The Release Desk is open, with the Blueprint's dates and the questions still outstanding.

Care

Care begins when the first release is in use. Plans run on one- or two-year terms. They cover support with response times in writing, training for new staff, changes as the business moves, and a regular view of what the software costs to run. Faults reported within ten business days of a release are fixed free under that release, before any care plan applies.

What We Won't Do

  • Bolt a chatbot onto a broken process.
  • Bill hours.

We won't promise a result we can't measure.

Principles

  1. Optimize the work before writing the software.
  2. Automating a broken process makes it break faster.
  3. Build for the people who use it every day, not for the demo.
  4. Your cloud, your accounts, your data.
  5. A named person approves every change, and every change is logged.

Glossary

Wikker Blueprint
The fixed-fee first step: two to four weeks of interviews and records, ending in a business optimization proposal and the Release 1 backlog.
Release
A piece of working software delivered in two to four weeks, fixed in price and scope before it starts, invoiced when it runs.
Release Desk
The record of every release: scope, price, agreed result, review, approval and measured result.
Re-rank
Reordering the remaining work between releases, in light of what the last one showed.
Care plan
Support, training and changes after the software is in use, on a one- or two-year term.