A useful first release
We agree what your team needs first and what can wait. Budget, milestones, responsibilities and changes belong in a clear written scope.
How we work
From problem to working system
Bring the work that is scattered, slow or difficult to manage. Together, we turn it into a practical system, with a preview where possible, a written scope and a clear handover.
The process
Seven stages. One shared direction.
- 01
Tell us what isn't working
Start with the work: the spreadsheet nobody trusts, the approval lost in WhatsApp, or the task your team repeats. You do not need a technical specification.
What you leave with: A clear problem and a shared definition of success.
- 02
We map your workflow
We work through people, permissions, records, approvals, reports and integrations. Together, we decide what belongs in the first release and what can wait.
What you leave with: An agreed workflow, project scope and delivery proposal.
- 03
See a working preview
Where practical, we create a free prototype or demonstration of the core workflow before a full-build commitment. We agree what the preview covers so you can assess the direction with your team.
What you leave with: A practical preview and a chance to shape the approach.
- 04
Build
Design, engineering, access controls and migration planning happen against the agreed scope. Review points keep your team involved as the system takes shape.
What you leave with: A tested system ready for the agreed launch checks.
- 05
Launch
We prepare deployment, agreed data migration and training with the people who will use the system. Access, key workflows and handover responsibilities are checked before go-live.
What you leave with: A working environment and a team prepared to use it.
- 06
Own it
Your business data stays yours. We hand over the custom deliverables, documentation and access agreed for the project, with data export and ongoing operation planned into the scope.
What you leave with: A portable handover with ownership and dependencies documented.
- 07
Grow when you're ready
Add modules, integrations or reporting when the business needs them. Choose optional care, managed operations or ongoing development, or run the system independently.
What you leave with: Your next phase, on your terms. No forced subscription.
Preview before commitmentReact to something
React to something
you can actually see.
A preview gives you and your team a way to test the direction before the full build. Where practical, we demonstrate an agreed workflow using sample data. It is a conversation about how your system should work, with room to change the approach.
We agree the preview's scope and format first. Production features, integrations, migration and delivery dates are covered by the project proposal.
Working principles
How we keep projects practical
Built with your team in mind
The people who will use the system help shape it. Their day-to-day tasks, permissions and decisions guide the design and review points.
Security from the start
Access, sensitive records, retention and recovery requirements are considered during planning and reflected in the agreed implementation.
A clear next step
Choose optional ongoing support or a documented handover to your team. Hosting, dependencies and support responsibilities are agreed before launch.
Ownership, clearly explainedYour business
Your business
remains yours.
You retain ownership and control of your business data and the custom deliverables agreed for your project. NMT retains ownership of its pre-existing frameworks, libraries, tools and reusable technology unless otherwise agreed.
- Defined before the build
- The written agreement identifies deliverables, source-code access, licences, third-party dependencies and handover responsibilities.
- Planned for handover
- Data export, documentation, account access and operation by your team or another provider are included as agreed in scope.
Questions
Frequently asked questions
Do I need a feature specification before contacting NMT?
No. Tell us what is difficult, slow or scattered in your current workflow. Discovery maps the people, records, permissions and decisions before we propose a system.
What does the free preview include?
Where practical, we prepare a prototype or demonstration around an agreed part of your workflow before you commit to the full build. Its scope and format are agreed first. A preview helps you assess the direction; production delivery, migration and support are covered by the project proposal.
How are cost and delivery dates agreed?
We set the scope, price, milestones and responsibilities in a written proposal. Complex projects can be phased. Any changes to scope, cost or timing are agreed with you before the additional work proceeds.
What will we own at handover?
You retain ownership and control of your business data and the custom deliverables agreed for your project. NMT retains its pre-existing frameworks, libraries, tools and reusable technology unless agreed otherwise. Source-code access, licences, documentation and handover requirements are set out in the written agreement.
Do we have to pay for ongoing NMT support?
No forced support subscription is required. Care, Managed and Continuous Improvement are optional arrangements. You can choose Independent handover and operate the system with your own team or provider. Hosting and third-party service costs still depend on the services you use.
Show us how your business works.
We'll help you see what its software could look like. Start with a conversation about the problem.