Make complexity legible
We document decisions, clarify boundaries and explain trade-offs in language people can use.
About Verdant Span Systems
Independent by design. Invested in what lasts.
We are a platform engineering company working across the United Kingdom, Europe and North America. Our role is to leave teams with foundations they can understand, operate and keep improving.
Our mission
Make critical software easier to change.
Verdant Span Systems designs cloud foundations that stay dependable while businesses change. We engineer platforms, delivery systems and operational patterns that make critical software easier to release, observe and scale.
Working principles
Thoughtful engineering, shared ownership.
Build with the people who run it
Operations, security and product engineers shape the design before it becomes someone else’s handover.
Prefer progress that can be trusted
Small verifiable steps make risk easier to manage and value easier to see.
A steady path
From a small practice to a connected studio.
First foundations
Started as an independent cloud architecture practice for teams moving critical services out of fragile environments.
Working across teams
Expanded into platform engineering and remote delivery partnerships across the UK and Europe.
Reliability in the work
Established dedicated reliability, observability and security practices alongside cloud foundations.
Built for what changes next
Partnering across the UK, Europe and North America with an emphasis on capability transfer and practical outcomes.
The people behind the practice
Thirteen perspectives. One shared standard.
A close-knit team of architects, engineers, designers and delivery partners who value clear thinking and useful work.
Eleanor Whitcombe
Founder & Principal Cloud Architect
“Good architecture makes change feel less expensive.”
Eleanor founded Verdant Span after years designing cloud estates for organisations with demanding operational and regulatory needs. She works from business constraints toward simple, explicit architecture, and enjoys helping senior teams make decisions they can explain as their systems grow.
Marcus Hale
Director of Platform Engineering
“A platform earns adoption by removing friction.”
Marcus leads platform engineering engagements, translating developer pain points into clear platform products. He has helped teams replace ticket queues with self-service workflows while keeping ownership visible. Away from delivery plans, he is usually sketching service boundaries or testing a new approach with engineers.
Priya Nanduri
Head of Reliability Practice
“Reliability starts with an honest conversation about risk.”
Priya helps product and operations teams turn availability hopes into service objectives they can use. Her work joins observability design with incident learning and capacity planning. She is particularly interested in the small operational habits that prevent a stressful outage from becoming a familiar one.
Thomas Avery
Cloud Security Lead
“Security should make the safe path easy to find.”
Thomas works with engineering and security groups to embed identity, policy and supply-chain controls into everyday cloud delivery. He prefers small, testable safeguards over lengthy checklists, and helps teams understand how a control changes their work before it reaches production.
Imogen Clarke
Delivery Director
“A good plan leaves room for what we learn.”
Imogen shapes engagements so that useful work reaches production in reviewable increments. She brings delivery, product and technical stakeholders into the same decisions, making risks and dependencies visible early. Her focus is on helping client teams carry momentum forward after a project closes.
Daniel Okafor
Principal Infrastructure Engineer
“The best module is the one another team can safely own.”
Daniel designs infrastructure foundations and reusable modules for services that need to stay operable over time. He is careful about interfaces, documentation and the edge cases that appear under load. In workshops, he makes complex infrastructure feel approachable without hiding its trade-offs.
Harriet Bowen
FinOps Consultant
“A cost line is useful when someone can act on it.”
Harriet helps organisations connect cloud bills to the products and teams making the decisions. She builds practical allocation and forecasting approaches, then works with engineers to identify waste without weakening service. Her favourite outcome is when cost conversations become routine rather than a quarterly surprise.
Samuel Reed
Platform Product Strategist
“Start with the person waiting for the platform.”
Samuel brings product discovery methods to internal platform teams. He maps developer journeys, listens for recurring friction and helps teams choose a first useful platform capability. His work balances adoption and operational boundaries so a platform roadmap remains connected to real engineering needs.
Aisha Rahman
Observability Engineer
“A graph matters when it helps someone choose what to do.”
Aisha designs telemetry that answers practical questions during everyday operations and incidents. She works across service metrics, event quality and tracing, helping teams remove noisy dashboards and agree on signals that reflect user experience. She also supports engineers as they build a habit of learning from production.
Oliver Grant
Cloud Migration Lead
“We rehearse the difficult day before it arrives.”
Oliver plans migrations around dependencies, data movement and the people responsible for cutover. He builds wave plans with clear rollback conditions and verifies assumptions before a date is committed. His measured approach helps teams modernise without losing sight of current service responsibilities.
Chloe Bennett
Developer Experience Designer
“Every repeated workaround is a design clue.”
Chloe studies how developers move from a change idea to a service in production. She combines interviews, journey mapping and prototype testing to make internal tools clearer and easier to adopt. Her designs give infrastructure capabilities a consistent interface and language that fits the team using them.
Nathaniel Brooks
Incident Response Specialist
“During an incident, clarity is a form of care.”
Nathaniel helps organisations prepare response roles, escalation paths and runbooks before an incident begins. He facilitates realistic exercises that expose communication gaps without blame, then turns the learning into focused follow-up. His approach helps teams stay calm while restoring service and keeping stakeholders informed.
Grace Linford
Client Partnerships Director
“Trust is built by saying what happens next.”
Grace looks after long-term client relationships, from the first exploratory conversation through delivery and transition. She makes scope, expectations and decision routes explicit so technical teams can focus on the work. Her practical partnership style is rooted in listening closely and following through consistently.