How we work, from first message to handover

We reply within one working day

Write to us through the website form, WhatsApp, email (info@red-sag.com) or phone. A few lines about what you want to build is enough. A developer or project lead reads it, not a sales script, and replies with first questions, a rough budget range where we can give one, and a suggested next step. Our working hours are Mon-Fri: 9AM-6PM IST.

• A written reply from a person who understands the technical side
• Honest early feedback if the idea is outside what we do well

Before we see anything confidential

If you ask, we sign a non-disclosure agreement before the detailed discussion. You can send your own NDA or use ours. Nothing confidential, such as business plans, designs, data samples or partner details, needs to be shared until it is signed.

• Signed mutual or one-way NDA
• Clarity on who at RED SAG will see your material

Usually within a few working days of first contact

A video call on Google Meet (or Zoom or Teams if you prefer) where we go through your users, the main workflows, integrations such as payment gateways or accounting tools, any compliance constraints, your deadline and your budget. We ask many questions here because unclear scope is the main cause of late, over-budget software.

• Shared understanding of the must-haves versus the nice-to-haves
• A list of open questions and any risks we can see early

After the call, once open questions are answered

You receive a written proposal: scope described as features and screens, what is explicitly out of scope, assumptions, technology choices, timeline, team, milestones and the payment schedule. When the scope is clear enough we quote a fixed price. When it is not, we give an estimate range and suggest a paid discovery sprint or a time-and-material arrangement instead of guessing.

• Fixed-price quote or a clearly labelled estimate
• Milestones tied to things you can see working
• No obligation to go ahead

Optional, for larger or less certain projects

For complex products, such as lending platforms, marketplaces or anything touching regulated payment flows, a short paid sprint turns an idea into a specification: user flows, clickable wireframes, data model, integration research and a firm quote. You own every document and can take them to another team if you choose.

• Specification, wireframes and technical plan you own
• A firm quote based on real detail

Once you accept the proposal

We sign the agreement, which covers scope, IP transfer, confidentiality, milestones and payments. Payments are split across milestones, for example at kick-off, design sign-off, first working version and go-live; the exact split is written in your proposal. At kick-off we set up the code repository (in your account if you prefer), the project board and the communication channel, and agree who approves what.

• Signed agreement with milestone payment schedule
• Repository, project board and chat channel set up
• Named contacts on both sides

A demo every 1–2 weeks

Work runs in sprints of one or two weeks. At the end of each one we show you working software on a staging link, not slides, and you give feedback while changes are still cheap. Between demos you get short written updates on what was done, what is next and anything blocking us.

• Staging link you can click through at any time
• Regular written progress notes
• Early warning of risks to time or budget

Throughout the build, and before each milestone

Developers test their own work, and a second person tests every feature against the agreed scope on real devices and browsers. Critical logic such as payments, balances, tax calculations and permissions gets automated tests. Before a milestone is signed off, you test it yourself (user acceptance testing) and we fix what you find.

• Tested features matched to the agreed scope
• Your sign-off before milestones close

On a date agreed with you

We deploy to production, set up domains, SSL, backups, error monitoring and app store listings where relevant, and watch the system closely in the first days. For apps that replace an existing system, we plan data migration and a rollback path in advance.

• Live system with backups and monitoring switched on
• App store submissions handled with your developer accounts

At launch and final payment

You receive the full source code, all credentials and admin access, and documentation: how to set up and deploy the system, how it is structured, and how to use the admin side. Hosting, domain, app store and payment gateway accounts are in your name. Nothing is locked to us.

• Source code in a repository you control
• Credentials and account ownership transferred
• Technical and user documentation

For the period agreed in your proposal

After launch there is a bug-fix period agreed in your proposal. During it, we fix defects in the work we delivered, meaning anything that does not behave as the agreed scope describes, at no extra cost. New features and changes of direction are quoted separately.

• Defects in delivered work fixed without extra charges

Optional, monthly

Most software needs ongoing care: security updates, dependency upgrades, backups, changes when a payment gateway or tax rule changes, and small improvements. You can choose a monthly maintenance plan, book hours as needed, or have your own team take over using the documentation we hand over.

• A plan that fits how much change you expect
• Freedom to move the work in-house at any time