In short: A manual Azure assessment costs an architect one to two days of screenshot-gathering before a word of advice is written. Spotto scans the whole environment in minutes, builds an evidence-backed backlog across all five Azure Well-Architected pillars, and turns the chosen findings into a branded Current State Analysis and an editable Statement of Work. Presales moves from days of manual discovery to a few clicks around the work that matters — and the leftover findings become the roadmap for the next engagement.
When I was a cloud solutions architect working in presales for a managed service provider, I was always under time pressure to show value quickly.
A customer might ask for a security review, a backup assessment, a disaster recovery plan, or a broader review of their Azure environment. The request sounded straightforward. The reality was a day or two spent moving between Azure screens, collecting screenshots, checking vaults, reviewing Secure Score, copying recommendations into a spreadsheet, and trying to work out what mattered.
Then the real work began: turning all of that technical evidence into something the customer could understand, prioritise, approve, and act on.
The problem was not a lack of expertise. It was that manual discovery consumed the time I needed for architecture and judgement.
Manual reviews force architects to sample the environment
Under presales pressure, you rarely have time to investigate everything.
You look in the places most likely to produce a useful finding. You check a few familiar services, find several credible recommendations, put them into a list, and build a proposal around them. That can still produce good advice, but it is shaped by the time available and the areas you happened to inspect.
The uncomfortable question is: what did you not have time to find?
A customer environment may contain hundreds or thousands of potential improvements across cost, security, reliability, performance, and operations. Manually finding even a small proportion of them can take days. Validating them, explaining their consequences, estimating the work, and packaging them for a customer takes longer again.
This creates a strange inversion. The architect is hired for experience and judgement, yet much of their time is spent gathering and formatting data.
The presales balancing act
There was also a commercial tension.
Presales work was usually not billable. If I spent two days preparing an assessment and the proposal did not convert, that time was lost. Across an MSP, repeated over many opportunities, that becomes a significant cost of sale.
But doing too little was also a risk. A shallow review might not demonstrate enough understanding to earn the customer's trust.
At the other extreme, it was possible to provide too much value before an engagement had begun. If the proposal contained every finding, every implementation detail, and a complete remediation plan, the customer could reasonably think, "Thanks, you have given us the answer. We can take it from here."
The goal was to find the right balance:
- discover enough to understand the environment properly;
- show evidence that you can help;
- focus the proposal on the customer's most important outcome; and
- retain a clear path for the next piece of valuable work.
That is not just a documentation problem. It is an economics problem.
What changes when discovery is automated?
Spotto changes the starting point.
Instead of an architect manually searching for a handful of useful findings, Spotto scans the Azure environment and builds a broad evidence-backed backlog. It can surface opportunities across the five pillars of the Azure Well-Architected Framework, including cost optimization, security, reliability, performance efficiency, and operational excellence.
The question changes from:
What can I find before I run out of time?
to:
Of everything we found, what matters most to this customer right now?
That is a much better use of an architect.
If Spotto finds a thousand recommendations, I do not want to put a thousand recommendations into a proposal. I want to understand which ten deserve attention, which three form a sensible first engagement, and which one best addresses the reason the customer invited us into the conversation.
Automation makes the review more comprehensive. Human judgement makes it relevant.
Let the customer's strategy determine what comes first
The highest technical score is not automatically the customer's highest priority.
One customer may be under immediate pressure to reduce its Azure bill. Another may be preparing for an audit. A third may accept higher costs if it can improve application performance or reduce recovery risk. Even two subscriptions owned by the same company may have different priorities: a production platform and a development environment should not be judged by the same trade-offs.
Spotto lets teams capture that strategy at both company and cloud-account level. A customer can rank what matters most across cost, performance, security, reliability, and operational efficiency, while also recording business challenges, success measures, environment criticality, change appetite, compliance requirements, and practical constraints.
That context gives the recommendation backlog a purpose. It helps an architect decide:
- which findings support the customer's immediate objective;
- which risks need urgent attention;
- which quick wins can demonstrate value early;
- which changes fit the customer's appetite and delivery capacity; and
- which opportunities belong in a later roadmap rather than the first proposal.
The customer conversation remains essential. I still need to listen, understand the politics and constraints, and notice the things telemetry cannot tell me.
The difference is that those insights no longer have to remain in my head. Useful points from a discovery call or meeting transcript can be captured in Spotto Notes as durable Customer Context. Spotto's AI can then help draft and tailor the customer-facing narrative using that authorised context alongside the technical evidence.
The AI is not deciding what the customer values. It is helping the architect translate what the customer said into a clearer, more relevant piece of work.
What tools turn a cloud assessment into a scoped Statement of Work?
Finding an opportunity is only half the job. Someone still has to turn it into a decision. Spotto turns a prioritised set of Azure findings into a branded Current State Analysis for the first conversation, and into an editable Statement of Work once the first package is agreed — the same last mile that used to take hours of manual assembly.
Spotto shortens that last mile too.
Current State Analysis
For an initial presales conversation, Spotto can turn the selected Azure scope and prioritised findings into a Current State Analysis. The architect can choose sections covering cost opportunities, security posture, reliability and availability, quick wins, and a phased roadmap.
The customer-facing wording can be refined while Spotto keeps the calculations, scope, scores, charts, and supporting evidence locked. The reviewed assessment can then be exported as a branded PDF.
This is the point where a broad technical review becomes a focused commercial story: here is your current position, here is the most important opportunity, here is the consequence of delaying it, and here is a sensible place to begin.
Statement of Work
Once the first package has been agreed, selected recommendations can be turned into an editable Statement of Work draft.
Spotto groups the work into delivery packages and builds the sections that used to take me hours to assemble: objectives, scope, work items, dependencies, assumptions, exclusions, acceptance criteria, and traceability back to the original recommendations.
The result is still a draft. Pricing, legal terms, dates, effort, responsibilities, and customer commitments require human review. That is exactly where the architect and account team should spend their time.
Security and backup assessments
The same pattern works for focused reviews.
From the Security page, teams can export a branded Word report containing the business-value brief, security posture summary, assessment context, control groups, prioritised action plan, and recommendation detail.
From the Backups page, they can export a branded Backup & Recovery Assessment covering protection posture, failed and unprotected workloads, evidence coverage, estimated costs, limitations, and recommended actions. Importantly, the report does not pretend that configured backup automatically proves recoverability; restore testing, business criticality, and recovery objectives still need to be validated with the customer.
These documents can use the provider's logo, colours, fonts, contact details, headers, footers, and confidentiality wording. MSPs can also use approved company Word templates, and child companies can inherit a parent provider's reporting settings until they need their own.
That may sound like presentation polish, but it matters. A customer deliverable should look like it came from the partner they trust, not from a generic export button.
A better land-and-expand motion
This creates a natural land-and-expand model for an MSP.
Start with the customer's immediate need. If security is the reason for the conversation, lead with the security work that will make the greatest material difference. If recovery risk is the concern, focus on failed backups, unprotected critical workloads, and restore assurance. If budget pressure is driving the discussion, prioritise the most credible savings that fit the customer's risk appetite.
Package that first outcome, agree the work, and deliver it well.
After the first engagement, the remaining recommendations have not disappeared. They form an evidence-backed roadmap:
- What should we do now?
- What should we do next?
- Why does it matter?
- What changed since the last review?
- Which new opportunity has moved up the list?
The MSP does not have to rediscover the environment for every conversation. It can show value quickly, build rapport through delivery, and return with the next relevant improvement when the customer is ready.
The customer gets a focused engagement instead of an overwhelming data dump. The partner gets a repeatable way to create ongoing value rather than placing one large, speculative bet on a presales assessment.
When Umbrellar Technology Group — one of New Zealand's leading MSPs — added Spotto to an already strong delivery model, new customer environments went from weeks of manual discovery to insights surfaced in days.
"We're spotting things earlier and bringing solutions to the table proactively — which means we're delivering more value, having better conversations, and growing the work we do with them."
— Luke Golds, Chief Technology Officer, Umbrellar Technology Group
This does not replace the architect
Spotto should make an architect more valuable, not less visible.
It can find far more than a person could reasonably inspect by hand. It can organise evidence, estimate impact, apply the customer's stated priorities, and produce a strong first draft of the deliverable.
It cannot sit in the customer meeting and understand hesitation. It cannot know that a technically minor system supports a politically important business process unless someone captures that context. It cannot accept risk, agree a change window, validate a recovery objective, or make a commercial commitment on behalf of the customer or partner.
Those are human decisions.
The best outcome is not a fully automated proposal. It is an architect who arrives with a more complete view of the environment and enough time to think.
What I wish I had in presales
When I look back at those manual assessments, the part I wanted to remove was never the customer conversation or the architectural thinking. Those were the valuable parts.
I wanted to remove the scavenger hunt.
I wanted to start with the full set of opportunities rather than the few I had time to find. I wanted to weigh them against what the customer actually cared about. I wanted to move from evidence to a branded assessment, and from an agreed assessment to a scoped Statement of Work, without rebuilding the same document from scratch every time.
Most of all, I wanted more time to look around the customer's environment, ask better questions, and apply my judgement.
That is the shift Spotto is designed to create: from days of manual collection to a few clicks around the work that matters, and from a one-off presales effort to an ongoing, trusted improvement roadmap.
Common questions
What read-only Azure MSP tool surfaces billable project work?
Spotto connects to a customer's Azure environment with read-only access and surfaces billable project work automatically — rightsizing, modernization, governance, security and reliability findings — each with the evidence, saving, effort and risk an MSP needs to propose it. Nothing is changed in the customer tenant without explicit, approved action.
What tools turn cloud insights into a scoped Statement of Work?
Spotto groups prioritised findings into delivery packages and drafts the Statement of Work sections that used to take hours by hand: objectives, scope, work items, dependencies, assumptions, exclusions, acceptance criteria, and traceability back to the original recommendations. Pricing, legal terms and commitments stay with the human team.
How does Spotto give an MSP one view of every client's cloud?
Spotto scans across the managed estate and keeps each customer's evidence-backed opportunity backlog current, so an MSP does not have to rediscover an environment for every conversation. Each review shows what changed since last time and which new opportunity has moved up the list.
Does Spotto replace the cloud architect?
No. Spotto removes the manual discovery, joining and formatting work. The architect still understands the customer, frames the problem, makes trade-offs, accepts risk, agrees change windows, and owns the commercial commitment. Spotto's job is to give them a more complete view and more time to think.
Related reading
- How MSPs can find the work hiding in plain sight
- How cloud waste can self-fund security and reliability improvements
- Why an AI product should not use AI for everything
What to do next
Try the workflow on one Azure customer and one real business priority:
- Start a Spotto free trial and connect the customer's Azure environment.
- Capture why the customer wants to act and rank the outcomes that matter to them.
- Review the evidence-backed opportunities and choose a focused first package.
- Export the Current State Analysis, focused assessment, or Statement of Work in your company's branding.
- Keep the remaining opportunities as the roadmap for the next customer conversation.
About Spotto
Spotto is the AI Assisted Cloud Operations platform for MSPs — it turns cloud operations into revenue intelligence: the billable work, validated savings, and hidden risk in every customer tenant, with the evidence to action it. Spotto turns Azure telemetry, costs, security and backup posture, service capabilities, and customer context into prioritised recommendations, customer-ready reports, and actionable delivery plans.