Services Consulting & support
IT consultancy
Independent technology advice, delivered as a written recommendation your team can act on, with or without us.
At a glance
- Includes
- Architecture and platform reviews, build-versus-buy and vendor assessments, a written roadmap
- Works with
- Your current systems, your team and the options you are weighing
- Delivered as
- A written recommendation and roadmap, with the reasoning set out
- Starts with
- A conversation about the decision in front of you
Fit
Is this right for you?
Usually the right call when one of these sounds familiar.
A decision with real consequences
A platform, vendor or architecture choice you want checked before committing.
Opinions that disagree
Different people recommend different answers and nobody can settle it.
A system nobody has reviewed
It has grown over the years and its limits are unclear.
No agreed plan
Priorities change from one month to the next and nothing is written down.
Not the right service? Need engineers to deliver the work: Team augmentation. Need a live system looked after: Maintenance.
Scope
Scope and what you get
Agreed with you in writing before work starts. Each piece of work has a matching thing you receive.
- What we do
Architecture and platform review
We study how your systems are built, where they are fragile and what constrains them.
What you receiveA review you can share
A written account of what exists, what works and what limits you.
- What we do
Options compared
Each realistic option is described on the same terms, with its trade-offs.
What you receiveA clear recommendation
One recommended option and the reasons for it, written so others can follow them.
- What we do
Build-versus-buy and vendor assessment
We compare building, buying and renting against your needs, skills and constraints.
What you receiveAn assessment on equal terms
Each vendor or approach judged against the same criteria, with assumptions stated.
- What we do
Roadmap and priorities
We turn the decision into an order of work, with owners and assumptions.
What you receiveA roadmap your team can follow
Priorities, sequence and assumptions on paper, usable by any team.
Use cases
Relevant use cases
Practical situations where this service is put to work. Open a card to see how it applies.
Choosing a platform before committing
A written comparison of the realistic options, so the choice is made on reasons rather than habit.
- Options compared on the same criteria
- A recommendation with the reasoning
- Assumptions and risks stated
Reviewing a system that has grown unplanned
A review of how the system is built today and where its limits are, ahead of any change.
- Parts and dependencies mapped
- Weak points and constraints listed
- Suggested order for what to address
Agreeing a technology roadmap
A plan that turns scattered requests into an ordered list of work your team can act on.
- Priorities agreed with the people who decide
- Dependencies and sequence shown
- Written so another team could carry it out
Sample use cases, drafted as placeholders. The Plethora team confirms the final list.
Process
How it works
Four stops, agreed with you as we go. Each shows what we do and what we need from you.
Understand
We doWe learn how your business, systems and team work today, and what you need to decide.
You doYou tell us the decision, share what you have and put us in touch with the people involved.
Recommend
We doWe set out the options with their trade-offs, then give a clear recommendation.
You doYou question the options and tell us what we have missed.
Plan
We doWe turn the chosen option into scope, order of work, owners and assumptions.
You doYou confirm priorities and name who owns each part.
Review
We doWe go through the written recommendation with you and answer questions on it.
You doYou decide what to act on, and whether you want help carrying it out.
Quality
Quality and handover
How the work is checked, accepted and passed to you.
Independent advice
We recommend what suits you, and the reasons are written down.
Assumptions stated
Anything we have taken as given is listed, so you can check it.
Written to be shared
The recommendation reads clearly to people who were not in the room.
A defined handover
The report, roadmap and working notes are yours to keep and use.
Tools
Tools and technology
Tools we use in delivery. We choose them to suit your team, and the list does not imply any partnership. Logos belong to their owners. Framework symbols show the references we draw on when reviewing. They do not mean certification, accreditation or endorsement.
- AWS
- Microsoft Azure
- Google Cloud
- Kubernetes
- ITIL-aligned practices
- ISO 27001-aligned controls
- NIST framework alignment
Engagement
Engagement and cost factors
Ways to work with us
A scoped review
One question or system reviewed, with a written recommendation at the end.
Advisory sessions
Regular conversations with an engineer who knows your context.
Ongoing support
Advice on call as decisions come up, agreed separately.
What shapes scope, timing and cost
- How many systems or decisions are in scope
- How much documentation already exists
- How many people we need to speak with
- Security, compliance and data-location requirements
- How much detail the roadmap needs
Scope and cost are confirmed with you in writing before work starts.
FAQ
Frequently asked questions
No. The recommendation is written so that any capable team can act on it, including yours.
We compare options against your needs and write down the reasons. The list of tools we know does not imply any partnership.
It depends on the size of the question. We agree the scope and timing with you in writing before work starts.
Yes. Reviewing existing systems, including ones built by others, is a common starting point.
Make the decision with the options in front of you. Start with a conversation.
Tell us what you need and we will come back with next steps.
Talk to usRelated