03 Delivery
Working software every two weeks
The only reliable signal that a software project is on track is software that runs. Percentage-complete reports are not evidence, and by the time they are wrong it is too late.
Step 1: Agree the cycle
Each two-week cycle opens with exactly what is being built, drawn from the discovery backlog and prioritised by you rather than by us.
Day 1Step 2: Build and test
Automated tests on the core paths as the code is written, because a suite added at the end documents the bugs rather than preventing them.
Days 2 to 9Step 3: Deploy to staging
Everything built in the cycle runs on a URL your team in Bareilly can open, with real data shapes rather than placeholders.
Day 9Step 4: Review with the actual users
Not with a sponsor. The people who will use it, doing something real with it, which is where most requirement changes originate and should.
Day 10Step 5: Re-prioritise in the open
A new request is swapped for something of similar size or added with a visible cost and date impact. Nothing is quietly absorbed or quietly dropped.
Day 10
04 Handover
What a real handover contains
The code is the easy part. A handover is judged the first time something breaks at nine on a Monday and you are the one holding it.
- The repository, in your name, with the full history rather than one squashed commit at the end.
- An architecture note explaining what talks to what and why, in language a new developer can read in an hour.
- The data model with its constraints and the reasoning, since this is the part that is expensive to change later.
- An API reference for anything another system consumes, including the error responses, which are always the undocumented half.
- A deployment and recovery runbook, with a restore that has been tested by actually restoring rather than by assuming the backup works.
- A recorded walkthrough, so the knowledge does not depend on one person answering a call.
- Where the software writes into the books, the proviso to Rule 3(1) of the Companies (Accounts) Rules, 2014, administered by the Ministry of Corporate Affairs, has required a non-disableable audit trail since 1 April 2023, with the eight financial year retention Section 128(5) of the Companies Act, 2013 requires.
- Where the application holds personal data, the Digital Personal Data Protection Rules, 2025, notified on 13 November 2025 by the Ministry of Electronics and Information Technology, apply, with the main obligations commencing on 13 May 2027.
05 Reference
Terms used on this page
- Discovery
- A fixed-price phase producing user stories, the data model, the integration list, non-functional requirements and an estimate range. Owned by you.
- Releasable slice
- The smallest version with which a real user can do real work, delivered before the rest of the scope is built.
- Non-functional requirement
- A requirement about how the software must behave rather than what it does: concurrent users, response time, uptime, recovery time.
- Total cost of ownership
- Written TCO: the three-year cost including hosting, maintenance, patching and change.
- Runbook
- The written procedure for deploying, monitoring, backing up and recovering the system. What makes a handover real.
- CI pipeline
- Written CI: the automated build and test run on every change, which stops a fix breaking something else silently.
- Data Protection Board of India
- The adjudicating body under the Digital Personal Data Protection Act, 2023. The Schedule to that Act sets fixed rupee ceilings rather than a share of turnover: up to ₹250 crore for failing to take reasonable security safeguards against a personal data breach, up to ₹200 crore for failing to notify the Board and the people affected, and up to ₹50 crore for a breach of any other provision. That is why consent, retention and access control are build decisions here rather than paperwork.
06 Questions
Custom software in Bareilly: FAQs
Discovery is quoted as a fixed price and produces the specification and the build estimate, so the estimate rests on a written scope. The build is then quoted against that specification: user types, integrations, whether a mobile client is needed. A business in Bareilly is quoted on the same basis as anywhere else, and the specification is yours to take elsewhere. Every quote states IncorpX professional charges; third-party costs such as domain, hosting and licences and any government fees are billed separately at actuals.
A focused internal application takes 3 to 5 months. A platform takes 6 to 12 months. You see working software every two weeks throughout, which is the only reliable way to know a project is on track.
No. Discovery interviews, two-week reviews and handover all run over calls and a shared staging URL from our base in Chennai, Tamil Nadu. Where a shop-floor or site walkthrough genuinely needs someone present, that visit is planned and quoted.
When a package fits at 80% or better, when the requirement is still changing weekly, when nobody internally will own it after launch, and when the three-year cost of ownership exceeds the licence cost of something that already exists.
Because an estimate without one is a guess, and a guess becomes a dispute in month four. Discovery produces the user stories, data model, integration list, non-functional requirements and an estimate range. You own it and may take it elsewhere.
You do, from the first commit, along with the design files, infrastructure configuration and deployment pipeline. The code is never held back as a bargaining position.
Chosen for the problem and for whoever maintains it afterwards. Typically PHP or Node.js with PostgreSQL or MySQL, React or plain JavaScript on the front, and a mobile client only where a browser genuinely will not do.
Usually the main point. We integrate through published interfaces wherever they exist, and where the software writes into the books it inherits the audit trail obligation in force since 1 April 2023 under the proviso to Rule 3(1) of the Companies (Accounts) Rules, 2014.
Designed in from the data model up. The Digital Personal Data Protection Rules, 2025 were notified on 13 November 2025, with the main obligations commencing on 13 May 2027, so purpose, consent records, retention and a deletion path are part of the schema rather than a later migration.
Yes, starting with an assessment rather than a rewrite proposal: what the code does, what the tests cover, where the risk sits, and what it costs to maintain against to replace. A rewrite is proposed far more often than it is right.
Next step
Tell us the problem, not the feature list.
You get an honest view on whether a package would do it, and if not, a fixed-price discovery producing the specification and the estimate. Yours either way.
Read by Dhanush Prabha, our CTO, not a form queue. Reply usually within one working day, in your time zone.
Nebin Binoy 
