FAQ
Questions, answered plainly.
Ownership, safety, timelines and how we work with your team.
FAQ
Questions, answered plainly.
Something missing? Ask it on the first call.
You do. When a milestone is paid for, the code, designs, data and accounts for it are yours. We work in repositories and hosting accounts under your name wherever we can, and hand over documentation with every release. Third-party licences, such as a paid theme or plugin, stay with their owners and are listed in the handover.
An MCP server gives an AI assistant a defined set of tools, not open access. Access is scoped with OAuth, starts read-only and every tool call is logged, so you decide what the model can see and do.
The Model Context Protocol is an open standard that lets AI assistants like Claude call tools and read data from other systems.
Yes. We can lead the build end to end, or join your team: working in your repositories, following your code review and release process, using your tools such as Jira, Slack and GitHub, and taking part in your sprints.
Discovery is a short, scoped first step. Its length depends on the size of the business and the number of tools involved, and we agree it with you up front. During a build you see working software at regular demos, with launch dates agreed in the written scope.
It depends on the scope. We do not work from a price list: after a short discovery we write down what will be built, what is not included and the price for it, and you approve that before work starts.
Whichever the agreed terms say for your project. The pricing model, the milestones and when each payment is due are written into the agreement before work begins, so there are no surprises later.
That depends on the scope. The written scope gives dates for each milestone, and you see working software at regular demos along the way, not only at the end.
Changes are welcome, and they go through a short written change request. We tell you what it affects in time and cost, and nothing extra is built or charged until you agree.
One person who can make decisions, access to the systems involved (or a short walkthrough of them), and a few real examples such as documents, orders or enquiries. We confirm the full list in discovery.
Support after launch is whatever the agreed terms say. That can include handover documentation, a fix period for issues found after release, and an ongoing maintenance plan, which is agreed separately if you want one.
Yes. We are based in Coimbatore and work with clients in India and abroad, remotely, with a written scope and regular demos.
Send us a message through the contact form. We reply within 1 working day with a few questions and, if it looks like a fit, a time for a short call. From there we agree a written scope before any build begins.
Confidentiality and data handling are covered in the agreed terms, and we can sign an NDA before discovery if you prefer. We use least-privilege access, keep credentials in accounts under your name where possible, and only touch the data the work needs.
AI governance means setting simple rules for how AI is used with company data: which tools are approved, who signs off what, and a record of what the AI did. Any business whose staff already use AI tools can benefit, because it reduces the risk of data leaking or wrong answers being acted on.
Often, yes. We start with an audit of what is working and what is not, then recommend fixing, redesigning or migrating, and write that into the scope. Rebuilding is only suggested when it is the better value.
For businesses looking at a long-term partnership, we can offer one small pilot project free of cost or at a reduced price. The size of the pilot, what it covers and any cost are agreed in writing first, like any other project, so both sides know exactly what to expect.
Contact
Let's map your business.
Tell us what slows your business down. We reply within 1 working day with a few questions and, if it's a fit, a call.