Telos Labs
Strategic Assessment · One bounded decision in 3 weeks

Build, buy, or kill.
Decided.

A decision process that shows what each credible option will cost, with real vendor pricing, and leaves you a sequenced plan for the path that wins.

Get the right decision before you commit a year of your team and six figures of spend to the wrong path.

Strategic decision being routed to a clear build, buy, or kill outcome
Who The Assessment is For

You don't need to start over. You need someone who understands the whole picture.

You have capable people, working systems, and data you trust. The next decision crosses too many boundaries for one owner.

The Strategic Assessment brings those decisions together and gives your team a clear path forward.

One senior view
  • Product requirements and workflows
  • The applications you already run
  • Build, buy, extend, or leave alone
  • Data and integrations
  • Application platform and hosting
  • Quality and security once it is live
  • Your team or a partner
  • Long-term cost to operate
One written decision. One sequenced plan.

Fragmented Foundations

Built at different times, by different teams. They operate in isolation, not as a unified whole.

Compounding Complexity

Every fix adds more complexity. The stack gets harder to understand, not easier.

Decision Gridlock

Too many options. No clear way to choose. Rebuild, buy, or extend all feel risky.

The challenge isn't options. It's knowing what's right.

One of these is sitting on your desk

The bottlenecks we see over and over.

These aren't edge cases. They're where most mid-size teams lose another quarter.

01

Build vs. buy, undecided for 9 months.

Every vendor pitch looks plausible. Every internal proposal looks expensive. Nobody can make the call stick.

02

Your CRM (Salesforce) bill keeps climbing, and no one can explain why.

You're being told to "consolidate" or "rebuild." Both are expensive. No one can tell you which is actually right.

03

A CTO who needs judgment, not hands.

You don't need another contractor. You need someone who's shipped this before and will tell you the truth.

04

No CTO, and no plan to hire one.

You want technology that meets your clients' bar for quality without building an engineering organization to get there.

Scope

Sized to the decision you're making.

One bounded decision
About three weeks
  • Build versus buy
  • Consolidate versus continue
Several products and systems
Six to eight weeks
  • Several products and existing systems
  • More than one technical owner
Both have the same method and deliverable: a written decision and sequenced plan.
What you walk away with

Not a deck. A decision.

Everything you need to commit with confidence or walk away with clarity.

01

The credible options, researched in proportion to the decision

Build, migrate, or consolidate. Each path includes real vendor pricing and what it will actually cost over time.

02

What each vendor will actually cost and the risks

Feature gaps. Lock-in risks. Not a generic comparison.

03

The hidden costs everyone misses

Migration effort, retraining, integration rebuild, and internal disruption, quantified before you commit.

04

A plan ready for your team to start on, with the first phase scoped

So you can execute, or take it to another team, with clarity and leverage.

How it works

The steps we take to go from kickoff to decision.

01

Understand

Interviews with the people who own the outcome, a walk through how the work actually runs, and a read of the plans and systems that already exist.

02

Inspect

The systems, code, integrations, data, and costs that the decision depends on. Fixes that can be made safely will ship as pull requests while we work.

03

Set the requirements

What the product or decision has to do, which parts are clearly yours to build, and the criteria for everything else.

04

Investigate the options

Build, buy, extend, application platform, and hosting, researched in proportion to the decision.

05

Decide with the owners

Recommendations are tested in working sessions with the people who will live with them.

06

Leave the plan

Sequence, costs, owners, decision gates, and the first phase scoped. Your team can run it with us, alone, or with someone else.

How the work holds up

Recommendations your team can check. Principles we build to.

Your team can check the work
  • Every recommendation rests on something checkable: a file, a configuration, a query, a bill, or what someone on your team told us.
  • Technical observations go to the people who own the systems first, for accuracy and context, before they go to leadership.
  • The current approach gets argued for as seriously as any change.
  • Confirmed prices and estimates are clearly marked.
  • Recommendations are tested in working sessions before the plan is written.
  • The plan is written to be executed without us.
Principles
  • 01 Enterprise grade outward, simplicity inward.
  • 02 A quality line every change passes.
  • 03 No lock-in on AI models.
  • 04 Do not build what is not needed.
  • 05 Sequence for speed and lower risk.
  • 06 Tools that make the team better at its work, not order-takers for an AI.
Real examples

Real decisions.

Every assessment ends with a written decision and a sequenced plan.

Services firm · CRM consolidation
Avoided $790K–$1.5M in five-year cost from a consolidation the firm was being pushed toward.

The client was being pushed toward Salesforce consolidation. Our analysis showed it would actually increase cost.

We identified a lower-cost build path with equivalent functionality and gave them the plan to execute it.

Growth-stage agency · AI roadmap
Shipped, not demoed.

A growth-stage agency with a 14-month internal build and three pilots that never made it out of staging.

We retired what wasn't working, picked the one workflow that compounds, and scoped the first two weeks of real work.

Why Telos, not them?

There is no strategy deck for how your business actually runs.

Dev shops

They start building before knowing if they should.

No vendor analysis. No cost modeling. You end up committing before understanding the decision.

Strategy consultants

You get slides.

Months of analysis, a 60-page report, and no one who can build the thing they recommended.

Telos

We give you the decision and the plan to execute it.

The people who make the recommendation are the people who can inspect the code, ship the fix, and lead the build. Senior judgment with engineers, product, and design behind it.

After the decision

What happens when the answer is build?

The plan
Sequence, costs, owners, decision gates, and the first phase scoped.

Your team runs it

Alone, or with someone else. The plan is written to be executed without us.

You continue with Telos

Two forms, either or both:

Technology leadership

Direction, a standing decision cadence, architecture and code review, product decisions.

Build capacity

Sized to the plan, and scoped separately from the assessment.

One bounded decision. When it prevents one wrong technology decision, it pays for itself immediately.

FAQ

Questions we hear before every engagement.

Your team knows the business and the systems better than we ever will. What it usually lacks is one person with the time and the mandate to hold the whole picture, real pricing from the market, and pattern recognition from having done this elsewhere. We bring those and work with the people who own the systems, so the decision is independent and your team can execute it.
Good. We test it against the requirements, total cost, integration needs, operating load, and the credible alternatives. If it holds, you get evidence and negotiating leverage. If it does not, you find out before the contract.
No. The research is proportional to the decision. If the capability is clearly yours to build, we say so and spend the time on how. If a product, application platform, or hosting option could cut time, cost, or operating load, we research and test the credible ones.
It is ready for leadership to decide and for the first phase to start. It has requirements, architecture, sequence, costs, owners, and decision gates. Build-level detail is produced during the build, once the path is known.
No. You own everything the assessment produces: the inventory, the findings, the pull requests, the requirements, and the plan. Production development is a separate decision. If you continue with us, it is scoped and invoiced separately from the assessment.
Sometimes. Work that is clearly yours to build and does not depend on unresolved platform, sourcing, or interface decisions can start once its requirements are agreed.
The people making the recommendation can inspect the code, ship a fix, and lead the build. That changes what gets recommended.

In a technology stalemate? Tell us where you're stuck.

We'll tell you how to move forward. No pitch. No commitment.