K Kiyansh
Book a call
04 · Mechanics & FAQ

The boring details, up front.

No surprises. Here’s exactly how a sprint runs — payment, ownership, what we’ll do, what we won’t.

Payment terms

50% deposit at kickoff, 50% on ship. Stripe invoice. If a sprint goes over our quoted timeline, you don’t pay the difference — we eat it.

Code ownership

You own the code from day one. We work in your repo on a branch. PR reviewed and merged on your side, on your schedule.

What counts as a bug

In the 14-day window after ship: anything that breaks the agreed scope is fixed at no charge. New requests are new scope. We’ll tell you which is which on the spot.

Ongoing maintenance

Optional flat monthly plan after the 14-day window. We take care of routine upkeep — dependency bumps, security patches, hosting health, and small day-to-day tweaks. New features and enhancements get scoped as their own mini-sprint, always with a conversation first.

Stack and tools

Backend, full-stack, cloud, data. Comfortable with most modern stacks. AI tooling on our side: Claude Code, Cursor, voice agents — the typing layer.

NDA / IP

Standard mutual NDA on request. Sprint-specific work is yours, including AI-generated code. We don’t reuse your code or specs elsewhere.

When we say no

We’ll decline a sprint if the scope is wrong, the timeline is unrealistic, or we’re not the right team. Better to lose the project than miss the ship.

How we communicate

Daily Loom video updates during a sprint. Async-friendly by default (email, Slack, your tool of choice). Live calls when a decision needs us in a room. No standups, no status meetings.

Back to How it works Book a call
© 2026 Kiyansh Group LLC · kiyanshgroupllc.comTexas, USA · remote-first