MongoDB, Express, React or Next.js, and Node.js. TypeScript throughout. The stacks both of our own platforms run on.
KeevaathTech/Services/Product development
CORE · KPD
Product development
Discovery through launch and the iteration after it, for applications with real users and a roadmap that continues past the first release.
What this is
Discovery through launch, and the iteration after it. For applications with real users, real data and a roadmap that continues past the first release.
Increasingly that means agentic systems, retrieval and evaluation harnesses, which is the work we do on our own platforms every week and not a capability we added to a list.
What we build on
MERN and MENN
Backend and API
Data modeling, authentication and authorization, authentication handoff between systems, third party and CRM integration.
Agentic systems
Reasoning across a request, calling tools, checking its own output, and logging every step so a wrong answer can be reconstructed.
Retrieval and evaluation
Grounding answers in your own material, and measuring output against a fixed set before any change reaches a user.
Mobile
Progressive web apps first, native iOS and Android when the product genuinely needs the device. We recommend the cheaper one when it is enough.
Automation
Workflow automation, AI agents and chatbots, business process automation, on n8n, Make or Zapier where a platform is the right answer.
How we build agentic systems
Four rules, arrived at by operating our own. Every run is replayable, because a wrong answer you cannot reconstruct is a wrong answer you cannot fix. The system stops before it guesses. Anything consequential waits for a person, so autonomy applies to the reasoning and not to the outcome. And output is measured against a fixed evaluation set before any change ships.
The pipeline that implements all four, with the self check stage and the logging that makes it auditable, is shown on the home page. What clients get is that same architecture, not a chat window bolted to a database.
How an engagement runs
Four stages, in the same order every time. Define, design, build, run. Scope changes and the order does not, and the sequence is set out on the home page with the durations for each.
Two things about it are worth stating here. Design covers interface and architecture together, because deciding the screens without the data model produces screens that cannot be built. And you see working software in a real environment every cycle, not a status report describing one.
How it is quoted
After discovery, never from a conversation. An estimate made before the problem is understood is a guess with a decimal point on it, and it becomes the number everybody remembers.
For reference, a first release of a multi-sided platform runs ninety to a hundred and eighty days of effort. Multi-market work adds thirty to fifty percent, and that uplift is not negotiable because it is where the difficulty lives.
If you arrive without a definition, the discovery sprint produces one in two weeks at a fixed price, and the fee is credited against the build.
Handover is part of the build
If your team inherits the codebase it should be legible without us. Documentation and a clean handover are included and never an upsell. We would rather you could leave than rely on the fact that you cannot.
Questions we are asked
Will you quote from a brief?
Not for a build. We will quote the discovery sprint, which produces the definition a real estimate requires, and credit the fee against the build if you proceed with us.
Can our team work alongside yours?
Yes, and it is often the right arrangement when the plan is to take the product in house. We agree who owns which parts up front so that review and merge do not become a negotiation.
Do you use AI to write the code?
We use modern tooling like any competent team, and every line is read by a person before it ships. Our own platforms are the ones we would be embarrassed by, which is a stronger incentive than any policy.
What happens if we want to leave mid-build?
You take the code, the documentation and the environment. It is written into the engagement, because a studio that makes leaving expensive is relying on the wrong thing.
Do you build native mobile apps?
Yes, and we will usually recommend a progressive web app first and tell you why. Native gets built when the product needs the device, not because it bills more.
Start with the discovery sprint.
Two weeks, a fixed price, and a definition a real estimate can be built from. The fee is credited against the build if you proceed with us.