Build: one accountable team across the full delivery surface.
For greenfield and expansion programmes. Manuel leads personally and assembles the squad required to ship: business analysis, UX, development, testing, change, and cyber. One backlog. One standup. One sponsor relationship.
Programme types Company 31 takes on.
Build is Microsoft-centred by design. These are the engagement patterns that recur.
- Dynamics 365 Sales, Customer Service, and Business Central rollouts.
- Microsoft Copilot adoption across operations and knowledge work.
- Azure migration from on-premises or legacy hosting.
- Power Platform at enterprise scale, with governance that holds.
- AI enablement grounded in real use cases, not platform tours.
- Data and reporting uplift, including Power BI, Fabric, and dataverse.
- SharePoint and knowledge retrieval for Copilot grounding.
The right people for the job, not the people on the bench.
Every Build engagement is assembled from a short list of senior specialists Manuel has delivered alongside before. Typical roles on a programme include:
Programme leadership
Manuel Re. End-to-end accountability for scope, budget, governance, and sponsor confidence. Present at every steerco.
Business analysis
Senior BAs who write requirements a developer can build from and a tester can verify against. No ambiguity handed downstream.
UX and service design
Designers who work to the real constraints of the user and the process, not a pattern library. Proof in the click-through.
Development
Certified Dynamics, Power Platform, and Azure engineers. Pair with the Microsoft Partner where one is in place.
Testing
Test leads who own the strategy and the automation. UAT planned against outcomes, not screens.
Change and cyber
Change specialists and a cyber lead. Adoption planned from day one. Cyber posture tracked against ISO 27001 and the Essential Eight.
How a Build programme runs.
-
Scoping fortnight
Two weeks to read the ground, align on outcomes, and produce a charter the sponsor signs. Fixed price.
-
Squad assembly
Named people, named roles, named start dates. The squad does not start until the charter is signed.
-
Delivery cadence
Sprints that match your operating rhythm. Demos every fortnight. Steerco monthly. Reporting that tells the truth, weekly.
-
Hand off
Knowledge transfer runs from week one, not the last sprint. Your team owns the product before the squad rolls off.
Monthly retainer. Named roles. No surprises.
Pricing is on request. Typical Build engagements sit within the five hundred thousand to five million dollar programme range and are priced as a monthly retainer plus named squad roles. The charter artefact produced in the scoping fortnight is the basis for the commercial.
No time and materials open-ended. No hidden partner markups. If a Microsoft Partner sits alongside Build, their commercial is visible to you and to us.
Build FAQ.
Who does the work?
Manuel leads every engagement personally. The squad around him is assembled per programme from a short list of specialists Manuel has worked with directly. No offshore pyramid, no junior resource swaps mid-programme.
How does Build sit alongside our existing internal team?
The squad integrates into your governance. Daily standups, sprint cadence, steerco, and artefacts live inside your systems. Company 31 does not run a parallel programme.
Do you work with Microsoft Partner resources?
Yes. Build commonly sits alongside a Microsoft Partner or implementation partner. Manuel handles the partner interface so your sponsor is not refereeing two vendors.
What does pricing look like?
Pricing is on request. Typical Build engagements sit within the five hundred thousand to five million dollar programme range, priced as a monthly retainer plus named squad roles.
How long does a typical Build run?
Six to eighteen months for a standard rollout, shaped by the scope agreed in the charter. Longer engagements are possible where the sponsor wants Manuel in place through benefits realisation.
Ready to scope a Build engagement?
Book a call. Manuel will ask what the programme is meant to achieve, what is in place, and what is missing. If Build fits, a scoping fortnight proposal follows inside forty-eight hours.