Pricing and Terms

Every engagement is priced in two parts: a fixed fee for the Wikker Blueprint, then a fixed price for each release, set before the release starts. You pay only for what is delivered.

The Wikker Blueprint

Fee
From C$12,000, fixed in the proposal
Length
Two to four weeks
Credit
Credited against the first release

How a Release Is Priced

Each release lasts two to four weeks and is priced before it starts, from the scope agreed for it on the Release Desk. The price does not move once the release begins. If the work turns out larger than one release, the remainder becomes the next release, priced separately, and you decide whether and when it goes ahead. A release is invoiced when it runs in your systems and the agreed acceptance check is done. No figure per release is published, because a release that connects two systems and a release that builds a client portal are different pieces of work.

Two Examples

  • A 60-person distributor · Blueprint plus six releases

    Blueprint: quoting and order entry, three weeks. Release 1: one intake form for every quote request. Release 2: prices built from current supplier costs and set margins. Release 3: online approval and signature for the customer. Release 4: signed orders passed to accounting without retyping. Release 5: stock reserved at the moment of order. Release 6: a weekly margin report for the owner.

  • A 25-person professional services firm · Blueprint plus three releases

    Blueprint: client intake and billing, two weeks. Release 1: a single intake record shared by every partner. Release 2: time and disbursements captured against each matter. Release 3: month-end invoices drafted from the record for review.

Illustrations of how an engagement is shaped · composites, not clients

Care Plans

Care plans run on one- or two-year terms and begin when the first release is in use. Each covers support with response times in writing, training for new staff, changes as the business moves, and a regular report on what the software costs to run. The fee and the response times are set in the proposal.

Payment Terms

  • You pay only for what is delivered. Each release is invoiced when it runs in your systems.
  • Faults reported within ten business days of a release's delivery are fixed free, and payment is never held back for a fault.
  • The result agreed for each release does not affect delivery, acceptance or payment.
  • The software runs in your cloud, under your accounts.

Why Every Release Carries a Result

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

A fixed price tells you what a release costs. The agreed result says what it is for: one measure, written down before work starts and reported once the software is in use. If a release cannot name what it should change, it is not ready to start.

Questions

Where does our data live?

In your cloud, under accounts you control. Wikker works inside them with access you grant and can withdraw.

What does a fault cost in the first ten business days?

Nothing. Faults reported within ten business days of a release's delivery are fixed free, and payment is not held back while they are.

What is a result agreed in advance, and what is it not?

It is one measure, agreed before a release starts, of what the release should change, reported after it is in use. It is a goal, not a guarantee, and it does not affect delivery, acceptance or payment.

Can the software include AI?

Yes, where it does a defined job, such as drafting documents, classifying records or forecasting demand. A named person approves every change it proposes, and every change is logged.

What does the software cost to run?

The cloud and service costs are yours, billed to your accounts, and the care plan reports them by process so they can be checked.

Is there a minimum size?

No headcount minimum. A Blueprint suits a business with a process worth the fee to fix, whether it has 15 people or 400.

How long does a care plan run, and what does it cover?

One or two years. It covers support with response times in writing, training, changes as the business moves and a report on running costs.

What if the Blueprint finds that no build is needed?

Then it says so, and nothing further is owed.

Why is a release two to four weeks and not a date?

A short, fixed release keeps the price certain and lets you re-rank the work before the next one. A single date for the whole build would fix a plan made before anyone had seen the software in use.