When you need it
You have a plan, or at least a list: move off the old file server, stop approving purchases by email, get everyone on single sign-on, retire the last on-premises server. Each item is small, but nobody has the time to run them all, so they wait while licence costs, risks and manual work pile up. A transformation stalls when nobody is accountable for finishing it.
What sets the quote
- Focused, 12 weeks: one business area or site, up to 100 users and up to 3 initiatives.
- Company-wide, 24 weeks: up to 300 users and up to 6 initiatives across business areas.
- An initiative is one change of up to 3 weeks of build work, for example: a team's files moved from a file server to SharePoint or Google Drive; an email or spreadsheet approval replaced by a form and an automated workflow in Power Automate, Google AppSheet or n8n; single sign-on and MFA for your business apps; an on-premises server moved to the cloud; two systems connected through an API; or Microsoft 365 Copilot or Gemini for Google Workspace rolled out to one team, with sharing permissions cleaned up first.
- Platforms: Microsoft 365 or Google Workspace, and AWS, Microsoft Azure or Google Cloud.
- The starting point is a roadmap: the one from our cloud and digital roadmap, or your own plan, reviewed in week 1.
- Larger initiatives, such as a new application or a full cloud migration, are quoted as their own package and run inside the programme.
What changes
- One accountable lead runs the programme, so initiatives finish instead of waiting for someone's spare time.
- Every initiative has a measure agreed up front, such as hours of manual work, number of logins or licence cost, and you see it before and after.
- Paper, email and spreadsheet steps become workflows that record who did what.
- Single sign-on, MFA, least privilege and backups are part of each change, not added at the end.
- Your people know how to use what changed, because every change comes with a guide and training.
What you get
- Programme plan: the initiatives in order, with owners, dependencies, measures and a budget view
- A steering meeting every 2 weeks with your sponsor: status report, risk log and decision log
- Each initiative designed, built, tested and handed over by our lead architect and the specialists it needs
- A before-and-after measure for every initiative, collected in one results report
- For each change: a short user guide, one training session per affected team, and a named champion in each team
- Runbooks and admin documentation for everything built or changed
- Closing review: results, what is left on the roadmap, and the next 12 months
Choose the programme when you know what needs to change and need someone to get it done. If you don’t have a plan yet, start with the cloud and digital roadmap: its roadmap becomes the programme’s starting point. If you need senior advice for a few hours a month rather than delivery, the fractional architect fits better.
Not included
- Software, SaaS and cloud licences, and hardware
- Initiatives larger than 3 weeks of build work (quoted as their own package, such as a cloud-native web app or migration and resilience)
- Data warehouses, BI dashboards and analytics
- ERP or CRM implementation and configuration (we connect them to other systems through their APIs)
- Running tenders or negotiating with vendors
- Running the new services after handover (available as a care plan)
What we need from you
- A sponsor with budget authority who chairs the steering meetings, and an owner for each initiative.
- Time-limited admin access for each initiative: in Microsoft 365, the Entra roles the change needs (for example SharePoint Administrator or Application Administrator); in Google Workspace, a custom admin role; in the cloud, access to the account, subscription or project in scope.
- Your roadmap or plan, a licence overview, and a description of how each process in scope works today.
- About 2 hours per initiative from the people who do the work today, for interviews and testing.
How it works
Free 30-minute call, then a written fixed quote based on the tier, your users and the initiatives.
Weeks 1–2: review the roadmap, choose and order the initiatives, agree a measure for each, and take the before measurements.
Delivery in two-week cycles: each initiative designed, built, tested with the people who use it, and rolled out with training.
Steering every 2 weeks: progress, risks and decisions, and the next cycle agreed.
Final 2 weeks: the after measurements, the results report and the handover.
At a glance
- Duration
- 12–24 weeks
- Price
- Fixed quote after a free 30-minute call
- Delivered by
- Vetted specialists, with our lead architect accountable
Related services
Architecture call
A 90-minute working session with a senior architect on one hard architecture question, followed by a written memo with the recommendation and next steps within three working days.
Technology decision papers
A written recommendation on a platform choice that is expensive to reverse, such as Microsoft 365 or Google Workspace, an identity platform, an AI platform or a cloud, with licensing and costs worked out.
Cloud and digital roadmap
A review of your cloud, your workplace platform and your applications over three weeks, ending in a 12-month roadmap with effort and cost ranges, and one presentation to your board.