Fit call
A free 30-minute conversation about the product, the stage and the decision you are trying to make.
Outcome: a clear recommendation, even if the answer is that you do not need me. HOW I WORK · SCOPE · MILESTONES · HANDOVER
A clear way to work together.
You should know what is being built, what it costs, what happens when something changes and how you get the code at the end. This page is the short version of the working agreement I use on freelance and contract projects.
Kochi, Kerala · IST (UTC+5:30) · Remote worldwide
THE ENGAGEMENT
Five steps, each with something you can inspect.
The process is designed to surface disagreement early, not to hide it behind a weekly call.
Written scope
Goals, platforms, features, assumptions, exclusions, acceptance criteria and the order of work.
Outcome: a scope you can compare with another quote, line by line.Milestones
A small number of demoable milestones, each with a working build and a written note on what changed.
Outcome: progress you can see, not a status message.Build & review
Implementation, device testing, release checks and a short risk log that stays visible.
Outcome: early warning when something is likely to slip.Launch & handover
Store submission, release notes, credentials, documentation and a support or maintenance plan.
Outcome: you can operate the product without me holding the only key.01 · NO SILENT SLIPS
Bad news should travel faster than the deadline
Every project has uncertainty. The problem is not that a risk exists; it is that the client finds out too late to make a decision. I keep a short risk list with the likelihood, the impact and the next check. If a milestone is at risk, I flag it as soon as the evidence is clear, explain the cause and propose the options: reduce scope, move the date or add capacity.
Updates are written. They state what shipped, what is next, what is blocked and what changed since the last update. A working build or a commit link is better than a paragraph saying everything is on track.
WHAT YOU CAN EXPECT
The working terms, in plain language
- ✓A written scope
Goals, platforms, assumptions, exclusions and acceptance criteria before work starts. - ✓Milestone demos
A working build at agreed points, not only a status report. - ✓Early risk flags
A risk is raised when it is seen, with options rather than a surprise. - ✓Direct communication
You talk to the person writing the code, without an account-manager layer. - ✓Code access
Your repository and accounts stay yours, with a clean handover at the end. - ✓NDA and IP terms
Confidentiality and ownership agreed in writing before detailed work begins.
02 · COMMERCIALS & OWNERSHIP
You should be able to leave cleanly
Most work is a fixed price per milestone for a defined scope, a monthly retainer for an evolving product or a block of hours for a specific piece of work. The model follows the work, not the other way around. The pricing guide explains the drivers and the planning ranges; the actual quote comes after a written scope.
On final payment, the source code, credentials and documentation transfer to you unless we agree otherwise in writing. I do not hold the repository or the release process hostage. If you need an NDA before sharing details, I can sign one.
WHAT I NEED FROM YOU
The project moves faster when these are clear
- ✓A decision-maker
Someone who can approve scope, priorities and release decisions. - ✓Access
Repository, staging, store consoles and third-party accounts when the work needs them. - ✓Feedback windows
A predictable time to review builds and answer questions. - ✓Content and design
Assets, copy and designs in a usable format — or a decision to scope them. - ✓A reproducible issue
Steps, device details or a recording for bugs; guessing is expensive. - ✓A named owner
One person who owns the product relationship and the final call.
COMMON QUESTIONS
Working together
How does a project start?
With a short fit call or a written brief. I review the product, stage, platforms and constraints, then propose whether a scoped project, a retainer or a smaller audit is the right next step.
Do you sign an NDA?
Yes, when you need one. I can sign a mutual NDA before detailed product, repository or commercial information is shared.
Who owns the code?
You do, on final payment, unless we agree otherwise in writing. The repository, credentials and documentation are part of the handover.
What happens if a milestone slips?
I flag the risk as soon as I see it, explain the cause and propose the smallest safe way to recover. I do not wait until the deadline to report a slip.
Can you maintain the app after launch?
Yes. Maintenance can be a monthly retainer, a block of hours or a release-support window. The scope is written down, including response targets and exclusions.
Do you work with clients outside India?
Yes. Most work is remote, with written updates and agreed overlap windows. I am based in Kochi on IST (UTC+5:30).
Can you take over an existing app?
Yes, after an audit. I review the codebase, release setup, accounts and known issues before agreeing to a timeline or a maintenance scope.
Do you guarantee a delivery date?
I commit to written milestones and early risk flags, not a blanket promise that nothing will ever change. If a date is at risk, you hear it early and we decide the trade-off together.