How we work
A defined project, an ongoing team, or support for a live system. Choose what fits your stage.
“I know what I want built.”
Not for work where the requirements are still moving — a retainer costs you less.
Scope a project →“I need a team, not a one-off.”
Not for a single well-defined build — a fixed-scope project is cheaper and simpler.
Talk about a retainer →“It's built. It needs an owner.”
Not for greenfield work — if nothing exists yet, start with a scoped project.
Get technical support →Plan your budget
AI systems and custom integrations are quoted around the use case and deployment needs.
Build Foundry is a registered micro enterprise (Udyam MSME) but is not GST-registered, so invoices carry a Udyam number rather than a GSTIN and no GST is charged. That also means there is no input tax credit for you to claim. If your finance team needs one, tell us in the first message rather than finding out at the invoice.
Get a scoped estimate →A few pages, your information and photos, and a contact form. Built on a solid template with your branding, and set up properly so Google can find you.
1–2 weeks
Designed for you rather than adapted from a template. More pages, a blog or gallery, enquiry forms, and real work on speed and search.
3–5 weeks
Bookings, payments, customer logins, an area only your staff can see. The point is what people can do on it, not what it says.
6–12 weeks
Several kinds of user, approval steps, documents and certificates, other systems connected to it.
3 months and up
Fixes, security updates, small changes, and an engineer your team can raise things with.
ongoing
These are ranges from work of this shape, not quotes. What moves the number is how many other systems have to connect, whether old information needs moving across, and how much has to be designed from scratch rather than adapted.
Larger platform projects often cost ₹12,00,000 – ₹15,00,000 and take six months or more. For bigger projects, we’ll check whether we have enough people and time to deliver.
Integrations, data migration, security requirements, design complexity, and support hours affect the scope. We agree these with you before quoting. Design and ongoing support are priced separately.
From first conversation to live product
Understand
We learn how your business works, who will use the product, and what gets in their way. We review existing tools and agree what a useful first version should achieve.
Share your goals, constraints, and examples of how things work today.
Deliverables are agreed around your project’s scope.
Understand
We turn the goals into a practical scope, choose how the parts will connect, and break delivery into milestones. Dependencies and trade-offs are discussed before the build starts.
Confirm the priorities, budget, and scope before we move ahead.
Deliverables are agreed around your project’s scope.
Create
We map the important journeys and design the screens around them. Loading, empty, and error states are considered too, so the experience works beyond the ideal scenario.
Review the key journeys and screens while changes are still easy to make.
Deliverables are agreed around your project’s scope.
Create
We build in manageable pieces, connecting the interface, data, and integrations. For AI features, we check sample inputs and outputs as we go. You review working progress at agreed milestones.
Try the working version and give feedback against the agreed scope.
Deliverables are agreed around your project’s scope.
Release
We test the important tasks, permissions, and failure cases, using automated checks and hands-on review. We check performance, fix issues, and make any remaining limits clear before launch.
Check that the key workflows fit the way your team and customers will use them.
Deliverables are agreed around your project’s scope.
Release
We prepare the live environment, check configuration, and release the tested version. A repeatable deployment process and a way to restore the previous version help keep the launch controlled.
Agree the launch window and confirm the final checks with us.
Deliverables are agreed around your project’s scope.
Ongoing care
We set up visibility into errors, availability, and performance. Alerts are tied to agreed thresholds, with clear steps for investigating problems and keeping the right people informed.
Agree who should receive alerts and which issues matter most to your business.
Deliverables are agreed around your project’s scope.
Ongoing care
Under an agreed support plan, we handle fixes, security updates, and upgrades. Feedback from real use helps us prioritise improvements, with larger changes scoped before work begins.
Share feedback from your users and help prioritise the next improvements.
Deliverables are agreed around your project’s scope.
Explore a stage above. Already have a product? We start with a review and agree which stages you need.
Included in every engagement
Tell us what exists, what needs to change, and when. We reply within one business day.