Skip to content
Kakoriya Cloud
Start a project Taking new projects ·

How we work

You see the plan, in writing, before you pay for anything.

The same four steps for a five-page website and a migration programme. Below them are the two documents every engagement produces — shown with fictional examples, because real ones belong to our clients.

  1. 01

    Conversation

    A call or a WhatsApp chat, or a written brief if you prefer. We ask about the outcome you need, the constraints you are under, and what has already been tried.

  2. 02

    Written scope

    Within two business days: a one-page scope with options, a fixed quote for each, the assumptions behind them, and what we would need from you.

  3. 03

    Build in the open

    Short milestones, with a demo or a written update every week. Decisions are written down as they are made, so nothing important lives only in a meeting.

  4. 04

    Handover

    Documentation, runbooks and decision records, so your team — or your next vendor — can carry on without us. Then a care plan, if you want one.

Step 02, in full

The scope note

One page, within two business days of our first conversation. Options side by side, a fixed price on each, and everything the price assumes — so you can compare us with anyone else on the same terms.

Scope note · v1

Example · fictional client

Client
A regional clinic group (fictional)
The ask
Patients should be able to book an appointment online, instead of only by phone.

  • A — Booking link

    A new five-page site with each clinic’s hours and a link to a hosted booking tool the clinics already pay for.

    2 weeks Fixed price

  • B — Integrated booking

    The same site with booking built in, reading live availability from the clinics’ scheduling system, plus SMS reminders.

    6 weeks Fixed price

Assumes

  • The scheduling system exposes an API with read access to availability
  • Clinic photos and copy are supplied by the client before week 2
  • Hosting on Azure Static Web Apps; domain stays with the client

We’d need from you

  • A named contact at the clinics who can approve copy
  • API credentials for a test environment

Step 03, in full

The decision record

Every choice that matters gets one: what was considered, what was chosen, why, and what it cost. It is the part of the work your team inherits — the reason a design can be changed safely later by someone who was not in the room.

Decision 07

Example · fictional client

Queue the order writes; do not call the ERP inline

Considered
  • Call the ERP synchronously on checkout
  • A nightly batch file
  • Queue each order, deliver to the ERP in batches
Chose
Each order goes on a queue with a correlation ID; a worker delivers them to the ERP in batches every few minutes.
Because
The ERP slows to several seconds a call at month end, and a customer should never wait on it. Batching also cuts the ERP's import runs, which is where most of its load comes from.
Gave up
An order is not in the ERP the instant it is placed. The site shows "received" until the batch lands, and support was told what that status means.

Terms we hold ourselves to

Four things that do not change

  • Written down, or it did not happen

    Scope, decisions and handover all arrive as documents you keep. Anything agreed on a call is confirmed in writing the same day.

  • Fixed price for fixed scope

    The quote in the scope is the price for that scope. If the scope changes, you get a new written option to accept or decline — never a surprise invoice.

  • The principal on every engagement

    Akshay Kakoriya scopes, designs and reviews every piece of work. Specialists who join are introduced by name before they start.

  • Yours at the end

    Code, infrastructure, domains and accounts are in your name from the first day. Nothing about leaving us is hard.