Dashboards, customer portals, internal business tools and SaaS products tailored to your workflows.
Clear apps get a fixed quote in the written scope. Uncertain ones start with a short paid discovery, which ends in written acceptance criteria and a fixed quote for the build.
A call, 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.
Within 2 business days: a one-page scope with options and the assumptions behind them, and a fixed quote for each, or a short paid discovery first if too much is still unknown.
Short milestones against acceptance criteria agreed in the scope. Decisions are written down as they are made, so nothing important lives only in a meeting.
Documentation, runbooks and decision records, with access and ownership in your name. Defects found after launch are fixed within a window agreed in your scope; ongoing support is a separate, optional agreement.
Paid discovery
Some apps can be scoped from one conversation. Others have open questions: who the users are, which journeys matter, what data and integrations are involved. A fixed quote built on guesses would only be a guess, so those start with a short paid discovery, quoted up front.
Timelines are planning estimates for a typical scope. Yours goes in the written scope, with a fixed quote for each option, within 2 business days of our first conversation.
For apps where too much is still unknown: roles, journeys, data and integrations worked through with you, ending in written acceptance criteria and a fixed quote for the build.
The core journeys, front end, backend APIs, database, sign-in, tests, deployment and documentation. Planned at 6 to 10 weeks or more, depending on scope.
Larger or multi-phase builds, quoted after discovery and delivered in phases.
From our founder’s previous employed roles, before Kakoriya Cloud, and labelled so. It is not the firm’s client work.
Founder experience
Customer platform · Energy utility
A utility’s public customer platform meeting its first real storm: what gave way, what the team changed afterwards, and which of those changes were our founder’s.
Done by our founder in a previous employed role, as part of a team, before Kakoriya Cloud.
It depends on the roles, journeys and integrations involved. A clear app gets a fixed quote in the written scope; an uncertain one starts with a short paid discovery that ends in a fixed quote for the build. Running costs are separate and billed by the provider.
A first version covering the core journeys is planned at 6 to 10 weeks or more, depending on scope. Larger builds are delivered in phases, each with its own acceptance criteria.
Because a fixed quote on unknowns is a guess. Discovery settles the roles, journeys, data and integrations first, and ends in written acceptance criteria and a fixed quote you can rely on.
Short, testable statements of what each feature must do, agreed before it is built. They decide when a feature is done, and any change goes through a written change request.
Repositories and cloud accounts are set up in your name from the start. Ownership of the code is as written in your agreement, including when it passes to you.
We build web apps that work well on phones. Native iOS and Android apps are not something we offer.
Defects are fixed within a window written into your scope. Ongoing support is a separate, optional agreement, described on the maintenance and support page.