Software development at Neoteric

Discovery that produces a plan, not a brochure

The first two to three weeks of every project are spent understanding the domain, the data and the integrations. The output is concrete: a domain model, a prioritised backlog, an architecture decision record and a milestone plan with acceptance criteria. Clients sign off on milestones, not on hours, so everyone knows what done looks like before the build starts.

Architecture that fits the problem

Our backends are Java and Kotlin on Spring Boot with PostgreSQL, structured around domain boundaries. We begin as a well-organised modular monolith and extract services only when a boundary has a real reason to scale or deploy independently. Kafka carries events between modules so integrations with ERPs, Tally, payment gateways and GST portals stay decoupled and auditable.

The best architecture is the simplest one that survives the next three years of change.

React and Flutter on the front

Web applications are built in React with TypeScript, consuming the same OpenAPI contracts the backend publishes. Mobile apps are Flutter from a single codebase, offline-first where the field demands it. A shared design system keeps the web and mobile experiences coherent, and Storybook keeps components honest.

Testing as a delivery habit

Unit, integration and contract tests run on every pull request; end-to-end flows run nightly against a production-like environment. Code review is mandatory and fast. Every release goes through a staging environment with real data shapes, and feature flags let us ship continuously while exposing features deliberately.

Milestones, demos and handover

We demo working software every two weeks and release to production in increments. Documentation, runbooks and architecture records are written as we go, so handover to an internal team is a formality rather than a project. Most clients keep us on for the next phase, but every one of them could run what we built without us.