Custom software, delivered by people who'll support it.

Integration work, principally. The most common engagements are joining business systems together — accounting to CRM, CRM to ticketing, line-of-business app to Microsoft 365 — through APIs, Power Automate flows, and custom middleware where the off-the-shelf connectors fall short. Beyond integration, we build custom extensions inside Microsoft 365 and Dynamics 365 Business Central: Power Apps for internal workflows, document automation against SharePoint, Dataverse-backed reporting. We are explicitly not a greenfield product-development shop — we don’t build SaaS products or take on multi-year engineering programmes. The honest limitation: if your project is a from-scratch consumer-facing application with novel UX or substantial mobile work, we’re not the right team. We’ll tell you that during scoping rather than take an engagement we can’t deliver well.

Our India development team writes the bulk of the code, working under Sydney-based technical leadership. Every project has a named Sydney solutions architect who owns the specification, the code review, and the production deployment — so the code shipped to your environment has passed through engineers we employ in Australia, not a hand-off across an arms-length contractor. Daily standups overlap with Australian business hours. Documentation, source control, and CI/CD pipelines all run from infrastructure under our direct control. The honest limitation: the timezone overlap is real but bounded — roughly four hours of daily overlap with east-coast Australia. For projects that need real-time pair programming or constant client-side collaboration we’ll either weight more of the work to the Sydney side (at higher cost) or recommend a different delivery model. We’d rather scope that explicitly than have it turn into a friction point later.

You do. Source repositories sit in your tenant or in a tenant transferred to you at handover — GitHub, Azure DevOps, or your existing system of record. The codebase, the build pipelines, the deployment scripts, and the documentation are all artefacts you own outright. There’s no Symsafe IP lock-in: no proprietary runtime, no hosted-by-Symsafe black box, no contractual obligation to keep us as the development partner. Where we use open-source components, the licensing is documented in the project README. Where we use commercial libraries on your behalf, the licence is in your name, not ours. The honest limitation: institutional knowledge isn’t transferable on a flash drive. If you take a complex codebase to a new development partner, expect a ramp-up period — we make that smoother by writing readable code with real documentation, but it isn’t zero.

Fixed-scope projects, typically 4–16 weeks. Every engagement starts with a written specification — what the system needs to do, what data flows in and out, what success looks like, what’s explicitly out of scope — and a fixed-price estimate against that specification. No coding begins until you’ve signed off on the spec, because that’s where the expensive mistakes happen. Delivery runs in two-week iterations with a running demo, so you see the system take shape rather than waiting for a big-bang release. Handover includes source code, documentation, deployment runbooks, and a stabilisation window where defects are fixed at no cost. The honest limitation: fixed-price only works when scope is genuinely defined. For exploratory work where the requirements will shift as you learn, we’ll quote a small fixed-price discovery sprint first and re-scope the build off that.