Schedule a consultation

Custom software

Custom business software

The full development process, run in the open — so you know what is being built, what it costs and what happens after it ships.

Custom software goes wrong in predictable ways: a vague brief, a price agreed before anyone knows the scope, months of silence, then a delivery that does not match what the business needed. Our process is designed around avoiding exactly that.

We charge for a requirements phase and produce a document that describes what the system does, who uses it, what it connects to and what is out of scope. That document is the basis of the estimate and the thing we are held to. If you decide not to proceed, the document is yours.

From there we design, build in reviewable increments, test, deploy and hand over with documentation. Maintenance is quoted separately so you can see what the ongoing commitment actually is.

What you receive

  • A requirements document you own
  • Designs and architecture approved before build
  • Working software at each review checkpoint
  • Test results and a migration validation report
  • Source handover, documentation and a support plan

Scope of work

What this engagement covers

Requirements & analysis

  • Process mapping of how the work is done today
  • User roles and their needs
  • Functional requirements and explicit exclusions
  • Integration points with existing systems
  • Data volumes, retention and reporting needs
  • A written document you own regardless of outcome

Design & architecture

  • Wireframes and screen flows for review
  • Data model and relationship design
  • Application architecture and hosting approach
  • Security, access control and audit requirements
  • Technology choices set out with reasoning
  • Scalability and maintenance considerations

Development & integration

  • Development in reviewable increments
  • Database implementation and optimisation
  • API design and third-party integration
  • Business automation of manual steps
  • Progress visibility at agreed checkpoints
  • Change requests assessed and priced openly

Testing, deployment & maintenance

  • Functional and user acceptance testing
  • Data migration and validation
  • Deployment to your environment
  • Handover documentation and training
  • Defect resolution period after go-live
  • Ongoing maintenance and enhancement arrangement

How we work

Working with us on this

How an engagement runs at Vanesh Nadar & Co. Four stages: review of the current position, a written scope and fee, execution to an agreed calendar, then review to stop problems recurring. STEP 1 Review We look at your records, filings, registrations and any open notices, and tell you plainly where things stand. STEP 2 Scope & fees A written scope: deliverables, timelines, what we need from you and the fee — agreed before any work starts. STEP 3 Execute Work carried out to an agreed calendar, with a named point of contact and documented handovers. STEP 4 Review & improve Recurring issues are traced back to the process that caused them, so the same problem does not return next quarter.
  1. ReviewWe look at your records, filings, registrations and any open notices, and tell you plainly where things stand.
  2. Scope & feesA written scope: deliverables, timelines, what we need from you and the fee — agreed before any work starts.
  3. ExecuteWork carried out to an agreed calendar, with a named point of contact and documented handovers.
  4. Review & improveRecurring issues are traced back to the process that caused them, so the same problem does not return next quarter.
Every engagement runs through the same four stages. Nothing begins until the scope and the fee are agreed in writing, and the fourth stage exists so that a problem found this quarter does not simply reappear in the next one.

General information only. The content on this page is general in nature and is not professional advice. Statutory applicability, thresholds and due dates depend on your specific facts and on the law in force at the time. Please speak to us before acting on anything you read here.

Questions

Frequently asked questions

How long does a custom build take?

It depends entirely on scope. A focused internal tool is a matter of weeks; a system replacing several existing processes is longer. We give a timeline after requirements, broken into milestones, rather than a figure before we know what is being built.

What if requirements change during the project?

They usually do. Changes are assessed for effect on scope, timeline and cost, and confirmed in writing before being taken up. What we avoid is silent scope creep that surfaces as a delay later.

Do we own the source code?

Ownership, licensing and source handover are agreed in writing before work begins, along with any third-party components involved and their licensing terms.

Can you maintain software after it is delivered?

Yes, under a separate maintenance arrangement covering fixes, minor changes, updates and a defined response arrangement. You are not obliged to take it, and the handover documentation is written so another team could.

Speak to a Chartered Accountant

Tell us what you need — accounting, tax, GST, audit, advisory, Zoho Books or a software build. We will come back to you with a clear scope and the next step.

WhatsApp us