Tell us what you are trying to build.
The more specific you are, the more useful the first reply will be. If you are not sure yet, book a call instead and we will work it out on the call.
Before you ask. Price, time, ownership, and what we turn down.
What does a project cost?
Websites from $2,400, web applications from $4,500, AI systems from $5,500 after a paid scoping phase. Design adds 20% of the build.
Fixed, quoted before we start, and it does not move unless the scope does.
No hourly billing, no change orders appearing halfway through, no handover that leaves you dependent on us.
What happens if the scope changes?
If the scope changes later we requote before doing the work, not after.
On web applications: complex applications are quoted individually and we will tell you before you pay if the scope has grown.
How long does a project take?
Four to six weeks for a typical website build.
For a website: scope in week 1, design in weeks 1 to 2, build in weeks 2 to 5, launch in weeks 4 to 6.
An application or an AI system is scheduled in its own written scope, before anything starts.
What ships with every build?
A written test suite. An accessibility audit against WCAG 2.2 AA. A performance budget the site has to pass. Security checks before launch. Documentation. Accounts in your name.
None of that is an upsell. It is the difference between something that was generated and something that was built.
We run the audit and the checks ourselves, and hand over what was tested and what was found. We do not certify compliance with any standard or regulation.
Who owns the code and the accounts?
You do: on final payment the work product and the accounts it runs on transfer to you.
Repository, hosting, domain, analytics, every account in your name. A written record of how it works and how to change it.
Can our own team run and change it without you?
Every account in your name, documented, with nothing that requires us to keep existing.
On websites: content lives in files in your repository. There is no CMS to log into unless you ask for one, and no subscription to keep paying.
On web applications: documentation of how it works, written for the next developer, so nobody is guessing.
On AI systems: the work is in the architecture, the tests, the permissions and the handover that let your team run it without us.
What happens after launch?
Thirty days of support afterwards, included. Bugs are ours to fix. New features are a new project.
What happens before any work starts?
One call, then a written scope with a fixed price and a date. Signed before any work starts.
We work out what the site or system actually has to do, who it is for, and what would count as it working.
Scoping is free on websites and web applications. On AI systems: every engagement starts with a paid scoping phase, because the honest answer to "can AI do this" sometimes turns out to be no, and you should find that out for a small amount of money rather than a large one.
Is there a written agreement before work starts?
Yes: client projects are governed by the separate written agreement signed before work starts.
Terms for client engagements are set out in the signed agreement for each project.
For client work, our liability is as set out in the signed agreement.
What if we do not know exactly what we need?
If you are not sure yet, book a call instead and we will work it out on the call.
Each service page gives its starting price, and we quote a fixed number once the scope is written.
What do you need from us?
Whatever exists already — brand materials, content, access to the systems it has to talk to. If none of that exists, say so. Gemnye sent us one paragraph about their company, and that was enough.
During design: one decision at the end of each round. Consult whoever you need to, then send us the consolidated answer.
During the build: final content, if you are supplying it, by the date the scope sets. If you would rather not write it, we can.
How do reviews and revisions work?
Two rounds of revision are included. A third is a change of scope, quoted before it starts.
You get a staging URL from the first week of the build. Look at it whenever you want.
Which AI providers do you build on, and who holds the accounts?
We build mostly on Anthropic’s Claude, through the Claude API, Claude Code and MCP, and on other providers’ models where a project calls for them.
Repository, hosting and API accounts in your name.
How are an AI system’s actions and permissions controlled?
Where a system acts, every action goes through a tool with a schema, a scope and an approval rule.
Where the system can call tools: a written map of what each tool may read and change, a person’s approval before any change is made, and a log of every call, kept in your account.
We document the controls; we do not certify compliance with any regulation.
Where are you, and which countries do you work with?
Kolkata, India. Our clients include a US e-commerce brand; we work with businesses in the US, UK, EU and Australia. We reply within one business day.
What do you not take on?
We do not take design-only work, logo-only work, or maintenance on sites we did not build.
On AI systems, we do not build customer-facing support chatbots. The evidence on those is poor, the failure is public when it comes, and we would rather turn down the work than sell you a rollback.
Who will actually do the work?
Amiya Bera, the founder, leads Kordal’s product and technical direction: how a system is scoped and structured, the interface and the design system it is built from, the application logic, APIs and data beneath it, and how it is deployed, tested and handed over.
Every project has one accountable lead from the first call to the handover, and specialists are brought in where the work needs them. You are told who, and when.
The work is hands-on. Amiya builds in the studio’s own stack. Rateslip, the Labs tools and this site were built that way, and the notes in Insights are written from them.