A method you can read before you commit to it.
The two fears a client brings to an Indian vendor are going dark and losing the IP. Both are answered here with a commitment rather than a reassurance. Publishing a cadence turns it into a promise, so only what we will actually hold every week is on this page.
How an engagement runs.
Scoping call
45 minutes. We ask what you are shipping, to whom, and by when. If software is the wrong answer we say so on the call.
Written proposal
Inside two working days: scope, platform, price, dates, and what is explicitly out of scope.
Discovery
A paid sprint when the scope is not clear yet. It ends with a spec and an estimate you could take to another vendor if you wanted to.
Build
Two week increments. A working demo at the end of each, a written update every Friday, and a shared channel you can reach us in during working hours.
Release
Store submission, review responses, phased rollout, and monitoring set up in your accounts.
- You own the IP. It transfers on final payment and it is written into the statement of work, not only the master agreement.
- We sign your NDA, or ours, before the first technical call.
- Repos, cloud projects and store accounts are created in your name on day one, and our access is revoked at project close.
Fixed scope build
One platform, one defined outcome: a v1 app, a Shopify app, a site rebuild, a WhatsApp integration.
- One quote against a signed scope, invoiced across milestones. Change requests are priced separately and approved in writing before anyone starts building them.
- Six to sixteen weeks for most first releases. Discovery sets the number before you commit.
- You own all source code, design files, accounts and IP on final payment.
Product retainer
A product that keeps shipping, or a team that needs mobile, Shopify or WhatsApp capacity it is not ready to hire for.
- A monthly retainer for a committed number of build days, planned one quarter at a time. Unused days do not roll forward, which keeps the plan honest on both sides.
- Three month minimum, renewed quarterly, thirty days notice to end.
- Work is committed straight into your repository, so there is never a version only we hold.
Discovery sprint
Two to three weeks to find out what should be built, or to review an app that is slow, crashing or failing store review.
- Flat fee for a fixed length. It converts into a build engagement at your option, and the fee is credited against the build if it does.
- Two to three weeks.
- You keep the spec and the report whatever happens next, including the parts that recommend not hiring us.
We price work, not hours. There is no rate card, because the number depends on the product, the platform and the scope. You get it in writing after the scoping call, against a signed scope rather than an estimate over the phone.
Read how we work in fullTesting is not the last week of the project.
Kyron was started by an engineer who spent five years in QA before writing production code: manual test design, Selenium, TestNG and SQL. That is why a written test plan exists before the first release, not a bug list after it.
Test plan per release
Written before the build starts, covering the paths that matter and the devices you actually sell to.
Regression before every submission
The same suite runs before each store submission, so version three does not break what version one did.
Device matrix
A mid range Android is the default test device, not the newest iPhone. Most of your users are on the former.
Crash and error monitoring
Set up in your accounts before launch, with alert thresholds agreed with you, not with us.
Questions we get before the first call.
Fixed scope for a defined build, a monthly retainer for a product that keeps shipping, and a paid discovery sprint when the scope is not clear yet. We price the work, not developer hours, and we do not publish a rate card because the number genuinely depends on the product, the platform and the scope. You get it in writing after the scoping call.
You do. The IP transfers on final payment and it is written into the statement of work. Repos and cloud projects are created in your name on day one, and our access is revoked at project close.
Monday to Friday, 10:00 to 19:00 IST. That is roughly 4.5 hours of overlap with London, 2.5 hours with a New York morning, and a full working day with Dubai, Singapore and Sydney.
Yes, yours or ours, before the first technical call.
Kyron Infotech is a member of the Shopify Partner Program. We are not a Shopify Plus Partner and we do not display a tier badge we have not been granted.
No. We build on the WhatsApp Business Platform as a developer on the Cloud API. Your business account, your billing and your message data stay with you.
Flutter when the product is the same on both platforms. Native when the platform APIs are the product, for example usage statistics, background services, widgets or sensors. We tell you which on the scoping call, including when the answer costs us the bigger project.
Tell us the platform and what you are trying to ship.
A 45 minute scoping call, then a written proposal with scope, price and dates inside two working days. Keval reads every enquiry and replies within one working day.
Email info.kyroninfotech@gmail.com
Or start a conversation on WhatsApp: +91 84889 97200