ISOMETRIC PARTNERS · ROANOKE, VIRGINIA

Start with one thing that takes too long.

We work with community banks, senior-care operators and contractors around Roanoke. They bring us one job that eats the week — loan documents read by hand, invoices matched line by line, the same customer question answered five times — and we work out what would actually fix it.

You do not need an AI strategy to talk to us. Bring one workflow, one archive, or one bottleneck.

Book a free 30-minute call See how we work

Thirty minutes with a partner, no charge. Roanoke, Virginia — we come to you or we meet online.

DIFFERENT PROBLEMS · DIFFERENT INTERVENTIONS
WORK
how work flows
INFORMATION
what you already know
AI
where it actually helps
SYSTEMS
tools that connect
02 / THE ISOMETRIC IDEA

See the whole system before changing it.

An isometric drawing shows three sides of an object at once. We look at a business the same way — the people, the steps they follow, the records they keep, the software they already pay for — before we suggest changing any of it.

What comes next depends on what we find. Sometimes it is a clearer handoff. Sometimes it is records people can finally search. Sometimes it is software that reads documents and drafts the reply for a person to check. Often it is no new technology at all.

Human-led systems, with technology doing the work it should.

PEOPLEthe team & its relationships PROCESSEShow the work actually flows INFORMATIONwhat the team knows TOOLS & TECHNOLOGYwhat enables the work DECISIONSwhere human judgment lives OUTCOMESwhat it is all for
03 / WHAT WE DO

Where do you need help?

Pick the sentence that sounds like your week. You do not need our vocabulary to start.

{{pn.tag}}

{{pn.quote}}

{{pn.body}}

  • {{c}}
    •

{{pn.start}}

{{n.label}}
04 / METHOD

Five stages, in order.

Stage 01 Understand: people, work, information and tools feed an observe and understand step that maps the current system and makes the invisible visible, surfacing friction and gaps such as handoff gaps, manual work and unclear or duplicate information System map: people, information, tools, meetings, handoffs and decisions with their relationships drawn, two bottlenecks marked, and the observed patterns listed Design stage diagram: the real constraint across people, information and work feeds a design decision evaluated on root cause, option fit and impact versus effort, producing clearer structure, a better tool, software worth building or the simplest path with no new technology, then a resolved system running from people through information, work and decision to outcome Build and test stage diagram: build together, test in real work, feedback loop and refine and iterate feed a working live prototype made of teammates, information, work and tools, with existing teams, work and context entering it and input from teams shaping the system Integrate stage diagram: connect systems, embed in work, refine handoffs and run reliably feed an integrated system in daily operation across teammates, information, work, tools and decisions, supported by documentation, ownership and support, so the system holds as part of everyday work PEOPLE TOOLS INFO PROPOSED INTERVENTION OUTCOME
STAGE {{stageN}} · {{stageName}}

{{stageBody}}

Nothing ships until the people who do the work have used it and said it helps.

05 / HOW WE PICK TOOLS

We do the research so you get the right tools.

There are thousands of AI tools and most of them will waste your money. We test the options against your actual work and bring back the few that hold up.

Every tool we recommend clears these six checkpoints first.

HOW WE VET A TOOL
CHECKPOINT {{prNum}}
{{prNum}}

{{prName}}

{{prQuestion}}

{{prDesc}}

IN THE SYSTEM
SOURCE OUTCOME
TESTED BEFORE IT REACHES YOU. You get the shortlist, not the search.
06 / ENGAGEMENT

Five ways to start

From a half-day look at one workflow to a system we build and stay with.

System Discovery

A short, structured look at how your work actually happens, and where a system could help.

Focused Prototype

One workflow, one working prototype. Small enough to test, real enough to trust.

System Build

Design and build a complete system, integrated into the way your team already works.

Advisory

A standing second opinion when you are deciding what to buy, build, or leave alone.

Workshop

Half a day with your team, mapping how the work really runs. Nothing gets built.

07 / WHY US

The person who studies the problem is the person who builds the fix.

Most consulting hands your problem from an analyst to a slide deck to a developer who never watched the work. Here the partner who sits with your team is the one writing the code.

SYSTEMS THINKING HUMAN OBSERVATION INFORMATION DESIGN TECHNICAL ARCHITECTURE CREATIVE TECHNOLOGY IMPLEMENTATION ONE SYSTEM
08 / THE PARTNERS

You work directly with a partner

Shawn Baako

Shawn Baako

CO-FOUNDER · AI AGENT SYSTEMS ARCHITECT

Shawn spent his first career managing other people’s money, at Morgan Stanley and then at Bayesian Investment Management, the Roanoke registered investment adviser he founded, where the strategies ran as software he wrote and stood behind. He brings the same two habits to every engagement: sit with the people doing the work until the job is understood, then say plainly whether it wants a purchase, a change to who does what, or something built. When it is something built, he is the one who builds it.

Running a registered investment adviser meant living on records and disclosure, with his own name on the line whenever the software made a decision. He learned there where to trust a system and where a person has to sign, and that lesson carries into any business where a mistake is expensive, regulated or not.

He designs and builds working software himself. The system that runs Isometric Partners’ own day, reading the mail, keeping the records, doing the research, and handing anything that matters to a partner for review, is his work, and so is Zestli, a travel product he is building on the same ideas. That is why his advice on what to buy holds up: he has built the thing the vendor is demonstrating and knows what it does on a bad day.

He serves on the corporate board of the YMCA of Virginia’s Blue Ridge, and holds a master’s in financial economics from American University. In his words: “Builder enough to care how it works. Operator enough to care if it helps on Monday.”
PN

Phat Nguyen

CO-FOUNDER · SYSTEMS DESIGN

Phat is the one who watches the work happen — who touches what, where a file gets re-typed, which step everyone quietly dreads.

Then he designs the fix so your team will actually use it, which is sometimes a screen and sometimes a change to who does what on a Tuesday.

Isometric Partners ISOMETRIC PARTNERS

Start with one system.

Book thirty minutes with Shawn or Phat. No charge, no pitch deck. You describe the job that eats your week, we ask questions, and you leave knowing whether it is worth building anything.

We use your email for the calendar invite and nothing else.

Book a free 30-minute call

Rather write first? operations@isometricpartners.com

Where do you need help?

Work — “The way we work is slowing us down.”

We follow one job from the moment it arrives to the moment it is finished — who touches it, where it sits waiting, what the waiting costs. Then we redesign the steps, before anyone talks about software.

We start by following one job through your team for a week.

Information — “We can’t find what we already know.”

Contracts in a shared drive, policy in an email thread, the real answer in one person’s head. We put the records where people go looking for them, and keep them findable after that person retires.

We start with the five questions your team asks most and cannot answer fast.

AI — “We think AI could help, but we’re not sure where.”

Some jobs suit software that reads and writes: loan files read by hand, invoices matched line by line, the same customer question answered for the tenth time. Plenty of jobs do not. We tell you which is which before you spend anything.

We start with a half-day look at three jobs you think a machine might take.

Systems — “Our tools don’t talk to each other.”

The scheduler, the accounting package and the customer list each hold a piece of the same job. We connect what you already pay for so the pieces meet, without a migration nobody asked for.

We start by listing every place the same fact is stored.

Team — “Our people are buried in manual work.”

We find the repetitive part worth handing to a machine and the judgment worth protecting. What you get back is your team doing the work only your team can do.

We start by counting the hours the repetitive work really takes.

Five stages, in order.

01 Understand

We observe how the work actually happens, who is involved, what they need, how information moves, and where friction appears. At this stage, we are not solving yet. We are building an accurate picture of the system as it is.

02 Map

We map the system — people, information, tools, and the relationships between them. Patterns and bottlenecks become visible.

03 Design

We design the intervention that fits — sometimes software, sometimes structure, sometimes no new technology at all.

04 Build & Test

We build a working component and test it with the people who will actually use it, iterating on what works in practice.

05 Integrate

The new piece becomes part of the complete system — embedded in daily work, supported until it holds.

We do the research so you get the right tools.

Checkpoint 01 — Source Integrity

Where does this tool get its answers?

We trace every option back to the systems it reads, then verify origin, accuracy, and recency. Anything that cannot show its sources does not make the shortlist.

Checkpoint 02 — Human Judgment

Who owns the decision it informs?

We test each tool against the calls your team actually makes, and keep consequential decisions with a named person. The tool prepares the work and shows its reasoning.

Checkpoint 03 — Privacy

What does it need to see, and where does that go?

We read the terms, map the data paths, and scope access to the minimum the work requires, so nothing sensitive ends up somewhere you did not choose.

Checkpoint 04 — Transparency

Can your team see what it did, and why?

We run each candidate on real cases and check the trail it leaves. If your team cannot audit it without a developer, it is not the right tool.

Checkpoint 05 — Fit for Purpose

Is this the right tool for the problem?

We take the time to research, test, and compare the options against your actual systems and needs. The goal is to find the most effective fit, adding capability where it matters without adding more tools, noise, or complexity to the work you already do.

Checkpoint 06 — Maintainability

Can your team run it, and does it hold up?

We test major scenarios and run evaluations so agents and systems behave consistently before and after handoff. We favor tools that fit what you already own, document the setup as we go, and hand over something your team can operate, extend, and repair.

Book a free 30-minute call with a partner, or email operations@isometricpartners.com.