Logo_Color
Login See how Verto works

Platform comparison

Verto vs edison365

edison365 is one of the most interesting UK-built PPM platforms on the market, a Microsoft 365-native solution that makes a genuinely compelling case to organisations already deep in the Microsoft ecosystem. This is a comparison between two UK companies that share many of the same values, serving many of the same customers. The differences are in architecture, governance depth and Microsoft dependency.

Untitled design (2)

Peer comparison

Both Verto and edison365 are UK companies, G-Cloud listed, and focused on UK public sector. The meaningful differences are in architecture, governance depth, AI cost and Microsoft dependency.

In short

edison365 is a capable UK Microsoft 365-native PPM platform with a strong Microsoft ecosystem argument. Verto is a purpose-built independent P3M governance platform. The choice comes down to whether you want a platform that lives inside Microsoft or one that stands independently of it — and how deeply you need your governance model to be built in versus configured.

The basics

What each platform is built to do

This is a genuine peer comparison between two UK-built platforms. Both have real credentials. The differences are architectural and strategic rather than about basic fitness for purpose.

edison365
edison365

A UK Microsoft 365-native PPM platform built on SharePoint, Teams and the Power Platform. Portfolio management, project management, benefits management and innovation management — all within the M365 environment. Microsoft ISV Partner. Founded Sheffield, 2016.

Positioning
M365-native PPM for Microsoft-first organisations
Founded
2016 — Sheffield, UK
Team size
~30 staff
G-Cloud
G-Cloud 14 listed
Architecture
Built on M365 / SharePoint / Power Platform
AI
Via Microsoft Copilot — additional licence
Unique feature
Innovation / ideas management module
UK pub sector refs
Growing — founded 2016
Verto Cloud
Verto

A dedicated P3M platform built for UK public sector over 17 years. Independent of Microsoft — integrates with M365 but does not depend on it. MoP, IPA, GovS 002 and Green Book aligned by design. Deployed in weeks without a major SI.

Positioning
Purpose-built UK public sector P3M governance
Founded
2009 — UK
Team size
UK-scale organisation
G-Cloud
G-Cloud approved
Architecture
Independent — integrates with M365
AI
Built in — no additional licence needed
UK pub sector refs
100+ UK gov clients

The Microsoft 365 question

M365-native: a genuine advantage and a structural dependency

edison365's Microsoft 365-native architecture is its most distinctive characteristic and its strongest sales argument. It is worth engaging with honestly rather than dismissing, because the argument is real in certain contexts and so are its limits.

The M365-native pitch is at its most compelling when your organisation has made a strategic decision to run as much as possible inside Microsoft's ecosystem. If your CIO has mandated "Microsoft first" and your teams live in Teams, SharePoint and Power BI, the argument for a PPM platform that sits inside those tools rather than alongside them has genuine weight in terms of adoption friction and integration simplicity.

Architecture: what M365-native means in practice
How each platform relates to the Microsoft stack
edison365 — built on Microsoft
📋SharePoint lists as data store
⚡Power Platform for workflows and automation
💬Teams tabs for user interface
📊Power BI for reporting
🤖Copilot for AI (separate licence)
When Microsoft changes these components, edison365 changes too
Verto — independent, integrates with Microsoft
🎯Purpose-built P3M database and platform
🔗Integration with Teams, Power BI, M365
🖥️Own UI designed for PMO and SRO users
📊Native reporting — not dependent on Power BI
🤖AI built in — no additional licence
Verto's roadmap is its own — not dependent on Microsoft's product decisions

The dependency question: M365-native architecture means that Microsoft API changes, SharePoint architecture updates, Power Platform pricing changes and Teams integration policy decisions can all affect how edison365 works — sometimes without notice. For a mission-critical portfolio governance system, that external dependency on a third party's product roadmap is worth factoring into a long-term procurement decision.

The AI cost question

Three licences vs one: what AI actually costs with edison365

AI is central to both platforms' positioning. The cost structure is meaningfully different and worth understanding before procurement.
Getting AI capability — what you need to licence
edison365 AI via Microsoft Copilot
+Microsoft 365 licence (already have)
+edison365 platform licence
+Microsoft Copilot licence (additional cost per user)
Verto AI — included
✓Verto platform licence
✓AI included — no additional licence required
✓No Copilot dependency

Microsoft Copilot is priced at a significant per-user monthly cost on top of existing M365 subscriptions. For an organisation evaluating edison365 on the basis of its AI capability, the total cost of ownership should include the Copilot licence for every user who will access AI features, not just the edison365 platform cost.

The dependency question

M365-native architecture means that Microsoft API changes, SharePoint architecture updates, Power Platform pricing changes and Teams integration policy decisions can all affect how edison365 works, sometimes without notice. For a mission-critical portfolio governance system, that external dependency on a third party's product roadmap is worth factoring into a long-term procurement decision.

Choosing the right tool

When edison365 is the stronger fit and when Verto is

edison365 is well-suited when…
  • Your organisation has made a strategic commitment to Microsoft-first and wants PPM to live inside M365
  • Adoption friction is the primary concern and Teams-embedded tools have the best chance of user uptake
  • Your CIO or digital team has strong Microsoft ISV preferences
  • Innovation and ideas management is a specific requirement alongside project and portfolio management
  • Your Power Platform skills in-house mean you can configure and maintain the platform yourselves
  • The Microsoft dependency risk is acceptable given your existing Microsoft investment
Verto is the stronger choice when…
  • You need portfolio governance depth — MoP, IPA, GovS 002 and Green Book alignment built into the platform architecture, not delivered through configured templates
  • Your AI requirement should not depend on an additional Microsoft Copilot licence cost
  • You want a platform whose roadmap is independent of Microsoft's product decisions
  • SharePoint list performance at portfolio scale is a concern
  • You need a deeper UK public sector reference base with 17 years of proven delivery
  • Vendor scale for a long-term mission-critical contract matters — ~30 staff vs a larger, longer-established organisation
  • Your governance model needs to be structurally embedded in the platform, not maintained in Power Platform flows

Side-by-side comparison

edison365 vs Verto: how they compare for UK public sector P3M

An honest comparison between two UK-built platforms, focused on the dimensions that matter most for public sector portfolio governance.

 edison365
UK company
 Yes — founded 2009 
 Yes — Sheffield, founded 2016 
G-Cloud listing
 G-Cloud approved 
G-Cloud 14
M365 native / embedded
 Integrates with M365 — not dependent on it 
 Yes — SharePoint / Teams / Power Platform 
MoP / IPA alignment depth
 Structural — built into platform architecture 
 Template-based — ask how deep it goes 
GovS 002 / Green Book alignment
 Native alignment 
 Configurable — not native architecture 
Stage-gate governance
 Built in — IPA aligned by design 
 Available — via Power Platform workflow 
Benefits management
 Yes — Green Book aligned 
 Yes — dedicated module 
Innovation / ideas management
Not a primary feature
 Yes — unique differentiator 
AI features
 Built in — included in platform 
 Via Copilot — additional licence cost 
Microsoft dependency risk
 Independent — own release cadence 
 Platform changes affect edison365 directly 
SharePoint scale limitations
Purpose-built database — no SharePoint ceiling 
 List architecture — known ceiling at scale 
UK public sector references
 100+ over 17 years 
Growing since 2016
Vendor scale
 UK-scale, 17-year track record
 ~30 staff, est. £2–5M ARR 
Governance embedded vs configured
 Structural — built into platform design 
Configured via Power Platform and templates 

Honest assessment

edison365: where it genuinely leads and where the questions sit

What edison365 genuinely offers
  • UK company, UK team — shared values and genuine understanding of public sector context
  • G-Cloud 14 listed — directly procurable through standard frameworks
  • M365-native architecture — the lowest adoption friction for Microsoft-first organisations
  • Innovation and ideas management — a differentiated capability not found in most P3M platforms
  • Benefits management module — a genuine capability worth evaluating in a demo
  • Microsoft ISV Partner status — credibility in the Microsoft ecosystem
  • Active product development and growing market presence
  • Teams-embedded UX — familiar environment for organisations living in Teams
Where the questions sit for deeper evaluation
  • MoP and IPA alignment delivered via templates and Power Platform — ask how structural it is vs configurable
  • AI requires a Microsoft Copilot licence — a third licence on top of M365 and edison365
  • Platform roadmap dependent on Microsoft's product decisions — SharePoint, Teams and Power Platform API changes have downstream effects
  • SharePoint list architecture has known performance limitations at large portfolio scale
  • Governance logic lives in Power Platform flows — maintenance and knowledge dependency risk
  • ~30 staff and est. £2–5M ARR — vendor scale for a long-term mission-critical contract
  • Founded 2016 — genuinely growing but with fewer years of deep public sector deployment evidence than Verto's 17-year track record

Before you commit

Questions to put to edison365 in your evaluation

Because edison365 and Verto are closer in intent than most of the tools in this series, the due diligence questions need to be more precise. These are the ones that will reveal the most material differences.

Due diligence questions for edison365
  1. Is MoP and IPA alignment structural, built into the platform data model, or is it delivered through configurable templates built on SharePoint and Power Platform? This is the most important governance question. Template-based alignment requires maintenance; structural alignment does not.
  2. Which AI features are available without a Microsoft Copilot licence, and which require one? What is the per-user Copilot cost at our likely user count? Reveals the true AI cost. If Copilot is required for meaningful AI functionality, it is a material addition to total cost of ownership.
  3. What happens to our portfolio data and governance workflows if Microsoft changes a SharePoint, Power Platform or Teams API that edison365 depends on? Forces a clear answer on the Microsoft dependency risk and what your contractual protection is.
  4. At what portfolio size, number of projects, data records, concurrent users, have customers experienced performance limitations related to SharePoint list architecture? SharePoint lists have a known ceiling. This question surfaces where that ceiling is relative to your portfolio size.
  5. Can you show us five UK public sector organisations using edison365 specifically for MoP and IPA-aligned portfolio governance, not just project management, with deployment evidence? Tests the depth of the P3M governance reference base rather than the broader project management customer base.
  6. For a multi-year mission-critical contract, what is your vendor scale, business continuity plan and financial position as a ~30-person company? A fair question that any responsible procurement team should ask of any vendor at this scale for a long-term contract.

Verto across the public sector

17 years of UK public sector P3M, independent and purpose-built

edison365 and Verto share UK roots and G-Cloud credentials. The difference is in depth of track record, independence from Microsoft's product decisions, and governance that is structural rather than configured.

17 years serving UK public sector

100+ government clients

G-Cloud approved & procurement-ready

MoP MSP & IPA aligned by design

Common questions

Questions buyers ask when comparing Verto and edison365

These reflect the questions most commonly raised when both platforms appear in the same evaluation, particularly in Microsoft-first public sector organisations.s.

Is edison365 available on G-Cloud for UK public sector procurement?

Yes. edison365 is listed on G-Cloud 14, making it directly procurable through standard UK public sector frameworks. Both edison365 and Verto are G-Cloud approved, so procurement eligibility is not a differentiating factor between them. The meaningful differences lie in governance depth, Microsoft dependency, AI cost and vendor scale, not in procurement route.

What does it mean that edison365 is Microsoft 365 native?

edison365 is built on top of Microsoft 365, specifically SharePoint, Microsoft Teams and the Power Platform. It sits inside your existing M365 environment rather than as a separate application. This means lower adoption friction for organisations already embedded in M365, and native integration with Teams and SharePoint. It also means that edison365's performance, architecture and future development are tied to Microsoft's product decisions. Changes to SharePoint, Power Platform APIs or Teams can affect how edison365 behaves, a dependency that a purpose-built independent platform like Verto does not carry.

Does edison365 require a Microsoft Copilot licence for AI features?

Yes. edison365's AI capability is delivered through Microsoft Copilot, which requires a Copilot licence in addition to both the Microsoft 365 subscription and the edison365 licence. For organisations that do not already have Copilot, this is a third licence cost to factor into total cost of ownership. Verto's AI functionality is built into the platform and does not require an additional Microsoft licence.

How deeply does edison365 align to MoP, IPA and UK government governance frameworks?

edison365 claims methodology alignment and includes templates and structures intended to support P3M governance. The question worth asking in an evaluation is whether that alignment is built into the platform's data model and workflow logic, or whether it is delivered through configurable templates built on SharePoint and Power Platform. Purpose-built alignment, where the governance model is embedded in the platform architecture — is fundamentally more robust than template-based alignment, which requires maintenance and can drift as your process evolves. Verto's alignment to MoP, IPA, GovS 002 and HMT Green Book is structural, not template-based.

What is the risk of a platform built on SharePoint lists at portfolio scale?

SharePoint lists, which underpin much of the M365-native architecture, have known performance and scalability limitations at scale. For organisations managing large portfolios with significant data volumes, reporting complexity and concurrent user activity, these limitations can become material. Purpose-built P3M databases are designed for portfolio-scale data from the ground up, without the ceiling that SharePoint list architecture introduces. Ask edison365 directly about the portfolio sizes where customers have encountered performance considerations.

What is the vendor scale risk of procuring edison365 for a long-term contract?

edison365 is a UK company founded in 2016 with approximately 30 staff and an estimated revenue of £2 to £5 million. It is a growing business with genuine momentum in the market. For multi-year mission-critical contracts, procurement teams should assess vendor scale and business continuity alongside product capability. A 30-person company, however strong its product, carries different concentration risk than a vendor with 17 years of public sector track record and the organisational scale that comes with it. This is a fair question to ask of any vendor at this scale for a long-term contract commitment.

Does edison365 have a benefits management capability?

Yes. edison365 includes a benefits management module as part of its portfolio management offering. This is a genuine capability and is worth evaluating directly in a product demonstration. The relevant question for UK public sector buyers is whether that benefits management model aligns specifically to HMT Green Book methodology and the evidence standards expected by IPA assurance, or whether it is a more general benefits tracking capability. Verto's benefits realisation is designed around UK government methodology from the ground up.

What happens to edison365 if Microsoft changes its SharePoint or Power Platform?

As an M365-native platform, edison365 is directly dependent on Microsoft's product decisions. Changes to SharePoint architecture, Power Platform APIs or Teams integration patterns require edison365 to adapt accordingly. Microsoft regularly evolves its platform, and changes that affect the underlying infrastructure can create unplanned work for the vendor and temporary disruption for customers. A purpose-built independent platform manages its own release cadence without this external dependency, its roadmap is driven by customer and governance requirements, not by Microsoft's product strategy.

Next steps

Evaluating edison365 alongside Verto?

Because these are both UK-built platforms with similar market positioning, the most useful comparison is a side-by-side demonstration focused on governance depth, specifically how MoP, IPA and Green Book alignment works in each platform, and what that means in practice for your PMO function.

Talk to our team See Verto in action

Verto Newsletter

Insights That Move Public Services Forward

Discover tools, stories, and insights that help leaders deliver meaningful change across their organisations.

Subscribe Now