Sample Roadmap FS-RM-SAMPLE
90-Day Business Roadmap™ — Review Copy
Rivera Facility Services · January 12, 2026 – April 12, 2026. Generated from a full sample assessment for internal review only.
- Exactly three strategic priorities
- Every priority traces to assessment evidence
- Closely related findings consolidated
- Dependencies sequenced correctly
- Every priority has a measurable Day-90 outcome
- Every week contains 2–4 actions
- Weekly actions support a strategic priority
- Workload is realistic for a small-business owner
- KPIs are measurable and targets are not shown as achievements
- AI recommendation matches actual readiness
- Recommendations fit company size
- Watchouts are evidence-based
Fabstone Solutions LLC
Fabstone 90-Day
Business Roadmap™
A personalized execution plan built from your Fabstone Business Assessment™ — three priorities, twelve weeks, and a measurable outcome for each.
Prepared for
Rivera Facility Services
Roadmap reference
FS-RM-SAMPLE
Industry
Professional Services
Business size
11-25
90-day period
January 12, 2026 – April 12, 2026
Primary focus
Clear the bottleneck limiting your capacity
Confidential. Prepared exclusively for Rivera Facility Services by Fabstone Solutions LLC. This Roadmap is a professional recommendation based on the information you provided and is not legal, tax, or financial advice.
Before you begin
How to use this Roadmap
This is a working document, not a report to file away. Six things make the difference between a Roadmap that changes how the business runs and one that gets read once.
Work it weekly, not all at once
This plan is sized for about 2–5 hours of Roadmap work each week, alongside running the business. Block the time in your calendar before Week 1 begins.
Three priorities — deliberately
Your assessment surfaced more than three opportunities. Only three made this Roadmap, because businesses that pursue everything usually finish nothing.
Phases build on each other
Days 1–30 create clarity, days 31–60 put standards into daily use, and days 61–90 make the change permanent and measurable.
Measure honestly
The success scorecard has a blank result column on purpose. Fill it in at Day 90 with what actually happened, not what you hoped would happen.
Adjust, don't abandon
If a week slips, move it — do not delete it. The order of the work matters more than the exact dates.
Reassess at Day 90
Retake the Fabstone Business Assessment™ on or after April 12, 2026 to see how your Business Health Score moved.
Your first move
Find where work waits longest — complete it by January 19, 2026. ≈2 hours. Supports Priority 1 · Capacity bottleneck.
Executive summary
Where you are, and where this quarter takes you
32
out of 100 at Day 0
30
out of 100 at Day 0
Foundational Business
Level 1 of 5
Your Business Health Score of 32 places Rivera Facility Services at Foundational Business. That is the starting line for this Roadmap, not a verdict — the next 90 days are about moving three specific things, not everything at once.
Fabstone selected clear the bottleneck limiting your capacity, make your core work repeatable, and cut the repetitive manual work as your priorities for this quarter. This is the size where informal coordination stops working and written process starts paying for itself immediately.
You described your biggest challenge as "Manual operations and inconsistent delivery". The plan addresses it through Priority 1 first, because that is where the assessment evidence pointed most strongly.
Everything here is aimed at your stated goal — improve operational efficiency — and is sized for roughly 2–4 hours of Roadmap work each week, alongside running the business.
This quarter in one line
Clear the bottleneck limiting your capacity — supported by two reinforcing priorities, delivered in twelve weeks, and measured against the scorecard on the success page.
Strategic priorities
Your three priorities for the next 90 days
Each priority was selected from your individual assessment answers, not your overall score. Related findings were consolidated so the plan stays focused.
Clear the bottleneck limiting your capacity
Operations · Capacity
Where you are today
Work backs up at a predictable point — waiting on an approval, a person, or a scheduling step — and that queue sets the pace of the whole business.
Where you'll be at Day 90
The main constraint is identified, measured, and reduced, so more work moves through without adding hours or headcount.
Why this made the list: Your Operations & Processes score of 25 was the strongest evidence for this. You also named this area directly in your own answers about where work gets stuck. It is also the area most likely to move your stated goal — improve operational efficiency.
How you'll know it worked: Measured reduction in the wait time at the identified bottleneck, sustained over four weeks.
Make your core work repeatable
Operations
Where you are today
Your most important work is completed differently depending on who is doing it and how busy the week is. The knowledge lives in habit rather than in a written process.
Where you'll be at Day 90
Your three highest-volume workflows are written down in plain language, followed the same way every time, and easy to hand to someone new.
Why this made the list: Your Operations & Processes score of 25 was the strongest evidence for this. You also named this area directly in your own answers about where work gets stuck. It is also the area most likely to move your stated goal — improve operational efficiency.
How you'll know it worked: Three core workflows documented and in active use, with the same steps followed on every job for four consecutive weeks.
Cut the repetitive manual work
Operations · Efficiency
Where you are today
A meaningful share of each week goes to repetitive tasks — re-typing information, chasing updates, and moving the same data between places.
Where you'll be at Day 90
The two most repetitive tasks are either removed, simplified, or handled automatically, and the hours saved are measured rather than assumed.
Why this made the list: Your Operations & Processes score of 25 was the strongest evidence for this. You also named this area directly in your own answers about where work gets stuck. It is also the area most likely to move your stated goal — improve operational efficiency.
How you'll know it worked: Two repetitive tasks eliminated or automated, with a measured before-and-after time comparison.
Why this order
Priority 3 depends on Priority 2: repeatable core work has to be underway before less manual work can hold. Starting them in the other order usually means redoing the second one. Everything else can progress in parallel — the order shown is where your attention should sit first, not a queue you have to finish before starting the next.
Phase 01 · Days 1–30
Stabilize & Prioritize
The first 30 days are about seeing clearly and settling the ground. For an established small business, that means understanding how the work really runs today, choosing where to concentrate, and getting quick, visible progress on capacity bottleneck rather than starting everything at once.
Objective for this phase
Understand how your core work actually runs, and get capacity bottleneck moving with visible progress by Day 30.
Find where work waits longest
Week 1Priority 1 · Capacity bottleneck
Follow five recent jobs and note the point where each spent the most time waiting rather than being worked on.
Why now: Capacity is set by the slowest step, and it is rarely the step people assume.
Owner
You, or a named team lead
Effort
≈2 hours
Complete when
Five jobs are traced and the common waiting point is named.
Measure the wait at that step
Week 2Priority 1 · Capacity bottleneck
Record how long work sits at the bottleneck across a normal week.
Why now: The baseline is what makes any later improvement provable rather than anecdotal.
Owner
You, or a named team lead
Effort
≈1.5 hours
Complete when
A week of wait times is recorded for the identified step.
Map your three highest-volume workflows
Week 2Priority 2 · Repeatable core work
List the work that happens most often and sketch each one as a simple numbered sequence of steps — no software, a single page each is enough.
Why now: Everything else in this Roadmap sits on top of these workflows. You cannot improve, delegate or automate a process you have not described.
Owner
You, or a named team lead
Effort
≈3 hours
Complete when
Three workflows exist as numbered steps on one page each.
Pick the single workflow costing you the most
Week 3Priority 2 · Repeatable core work
Compare the three maps against time spent, rework and customer impact, then choose one to fix first and note why.
Why now: Fixing one workflow properly beats improving three partially, and it gives you a template for the rest.
Owner
You, or a named team lead
Effort
≈1 hour
Complete when
One workflow is chosen and the reason is written down in a sentence.
Time your repetitive tasks for one week
Week 3Priority 3 · Less manual work
Track the tasks that repeat daily or weekly and record roughly how long each takes.
Why now: Without a baseline you cannot tell whether an improvement was worth it — and you cannot claim a saving you never measured.
Owner
You, or a named team lead
Effort
≈1.5 hours
Complete when
A one-week log exists with rough minutes per task.
Pick the highest-value target and check it is stable
Week 4Priority 3 · Less manual work
Choose the task with the best combination of time spent and predictability, and confirm the steps are consistent enough to improve.
Why now: Simplifying or automating an unstable task locks in the wrong version of it.
Owner
You, or a named team lead
Effort
≈1 hour
Complete when
One task is selected and its steps are written down.
Quick wins in the first 30 days
Raise one approval threshold
Pick the approval you always say yes to and set a limit below which it no longer needs you.
20 minutes
Write down the one process you explain most often
The next time you explain a task, write the steps as you say them. That first draft is your standard.
30–45 minutes
Create one reusable template
Take the message, quote or document you rewrite most often and save it as a template.
30 minutes
End-of-phase checkpoint
- Bottleneck identified from five traced jobs and baseline measured
- Three core workflows mapped and one chosen as the starting point
- One week of task timings captured and a target chosen
Phase 02 · Days 31–60
Build & Improve
With the picture clear, days 31–60 shift from mapping to doing. This is where the written standards go into daily use, the first hand-offs happen, and repeatable core work starts moving in parallel. Pilot with one team first, then extend once the process is proven.
Objective for this phase
Turn what you mapped into what you do: standards in daily use, the first hand-offs live, and repeatable core work underway.
Remove or delegate the constraint
Week 5Priority 1 · Capacity bottleneck
Depending on the cause: raise an approval threshold, pre-authorise routine cases, add a second trained person, or reschedule the step.
Why now: Most bottlenecks are policy or availability problems, not capability problems.
Owner
You, or a named team lead
Effort
≈3 hours
Complete when
The change is live and applied to all new work.
Protect the step from new load
Week 6Priority 1 · Capacity bottleneck
Make sure work you have redirected has not simply created a new queue somewhere else.
Why now: Bottlenecks move; a fix that shifts the queue is not an improvement.
Owner
You, or a named team lead
Effort
≈1.5 hours
Complete when
The next step downstream has been checked and is not backing up.
Write the standard version of that workflow
Week 6Priority 2 · Repeatable core work
Turn the map into a working standard: the steps, who does each one, what 'done' means, and the two or three mistakes to avoid.
Why now: A written standard converts your judgement into something the business can repeat without you in the room.
Owner
You, or a named team lead
Effort
≈3 hours
Complete when
The standard is written and has been used on at least three real jobs.
Standardize the second workflow
Week 7Priority 2 · Repeatable core work
Repeat the same format on the second workflow, reusing the structure so it takes noticeably less time than the first.
Why now: The second one proves the format works and starts turning documentation into a habit rather than a project.
Owner
You, or a named team lead
Effort
≈2.5 hours
Complete when
The second standard is written and used on live work.
Remove the unnecessary steps first
Week 7Priority 3 · Less manual work
Before adding any tool, delete steps that exist out of habit, merge duplicate entry, and cut approvals that never change anything.
Why now: Elimination is faster, cheaper and less fragile than automating a step you did not need.
Owner
You, or a named team lead
Effort
≈2 hours
Complete when
The task has fewer steps than it did and still produces the same result.
Automate or template what remains
Week 8Priority 3 · Less manual work
Use what you already pay for — templates, saved views, scheduled reports or a simple built-in automation — before buying anything new.
Why now: Most small businesses already own the capability they are about to purchase again.
Owner
You, or a named team lead
Effort
≈3 hours
Complete when
The task has run twice in its new form without manual rework.
End-of-phase checkpoint
- Constraint reduced and the downstream step checked
- Two workflows standardized and in active use
- The target task simplified and running in its new form
Phase 03 · Days 61–90
Optimize & Scale
The final 30 days are about proof and permanence: measure what changed, keep what works, and drop what did not earn its place. In professional services, this is the stage that decides whether the quarter produced a temporary push or a new standard.
Objective for this phase
Measure what changed, make the improvements permanent, and finish the quarter with results you can point to rather than intentions.
Re-measure and confirm the improvement
Week 9Priority 1 · Capacity bottleneck
Record wait times again over a normal week and compare with the baseline.
Why now: Only the second measurement tells you whether capacity actually improved.
Owner
You, or a named team lead
Effort
≈1.5 hours
Complete when
A second week of wait times is recorded and compared.
Identify the next constraint
Week 10Priority 1 · Capacity bottleneck
Once the first bottleneck clears, the next one becomes visible — name it for the next quarter.
Why now: Continuous capacity improvement is a sequence, not a single fix.
Owner
You, or a named team lead
Effort
≈1 hour
Complete when
The next constraint is named and recorded.
Standardize the third workflow and store all three together
Week 10Priority 2 · Repeatable core work
Finish the third standard and put all three in one place everyone can reach — a shared folder is fine.
Why now: Documentation only pays off when it is easier to look up than to ask someone.
Owner
You, or a named team lead
Effort
≈2.5 hours
Complete when
All three standards live in one shared location and the team knows where it is.
Run a consistency check on live work
Week 11Priority 2 · Repeatable core work
Review five recent jobs against the written standard and note any step that was skipped or changed.
Why now: Written and followed are two different things; this is how you find the gap while it is still small.
Owner
You, or a named team lead
Effort
≈1.5 hours
Complete when
Five jobs reviewed and the deviations are listed with a fix for each.
Measure the actual time saved
Week 11Priority 3 · Less manual work
Re-time the task and compare against your Week 1 baseline; record the real figure, not the projected one.
Why now: A measured saving is what justifies doing this again on the next task.
Owner
You, or a named team lead
Effort
≈1 hour
Complete when
Before-and-after times are recorded for the task.
Apply the same pattern to the second task
Week 12Priority 3 · Less manual work
Repeat eliminate-then-simplify-then-automate on the next task from your list.
Why now: The second one is where the approach becomes a capability rather than a one-off.
Owner
You, or a named team lead
Effort
≈2.5 hours
Complete when
The second task is running in its improved form.
End-of-phase checkpoint
- Wait time re-measured against baseline and the next constraint named
- All three standards documented, stored together, and verified against live work
- Measured time saving recorded and the pattern applied to a second task
Execution
Your 12-week plan
Every week names one focus, the priority it serves, the actions to take, and how you'll know the week worked. Budget roughly 2–5 hours per week.
Week
1
Locate the real constraint
Priority 1 · Capacity bottleneck · 2–3 hours- Trace five recent jobs end to end
- Note where each waited longest
- Name the common bottleneck
Outcome: The constraint identified with evidence · Five jobs point at the same step
Week
2
Measure the wait
Priority 1 · Capacity bottleneck · 1–3 hours- Record wait times at the bottleneck for a week
- Note the causes of the longest waits
- Set the baseline
Outcome: A measured starting point · You can state the average wait in hours or days
Week
3
See how the work actually happens
Priority 2 · Repeatable core work · 3–4 hours- List the work that repeats most often in a typical week
- Sketch your highest-volume workflow as numbered steps
- Note where the same step gets done two different ways
Outcome: A clear picture of how core work runs today · You can describe your busiest workflow in steps without improvising
Week
4
Reduce the constraint
Priority 1 · Capacity bottleneck · 3–4 hours- Change the policy, threshold or staffing at that step
- Apply it to all new work
- Watch for exceptions
Outcome: A materially faster step · No job waited longer than the new target this week
Week
5
Turn the best version into the standard
Priority 2 · Repeatable core work · 3–4 hours- Write the standard version of your highest-volume workflow
- Define what 'done' means at each step
- Share the draft with anyone who touches the work
Outcome: One written standard ready for live use · The standard has been used on a real job without edits
Week
6
Stop the queue moving elsewhere
Priority 1 · Capacity bottleneck · 1–3 hours- Check the next step downstream for build-up
- Adjust if a new queue appeared
- Name who monitors flow
Outcome: Flow improved across the whole path · No new bottleneck appeared downstream
Week
7
Find where the hours actually go
Priority 3 · Less manual work · 2–3 hours- Track repetitive tasks and rough minutes for one week
- Rank them by total weekly time
- Note which are predictable enough to improve
Outcome: A ranked, time-based target list · You know your top repetitive task in minutes per week
Week
8
Put the standard into daily use
Priority 2 · Repeatable core work · 2–3 hours- Use the standard on every job this week
- Capture anything that did not match reality
- Update the standard once at the end of the week
Outcome: The standard reflects how the work truly runs · No job this week bypassed the written process
Week
9
Simplify before you automate
Priority 3 · Less manual work · 2–3 hours- Write the current steps for your top task
- Delete steps that add no value
- Confirm the shorter version still works
Outcome: A leaner version of the task · The task has fewer steps and the same result
Week
10
Give the process an owner
Priority 2 · Repeatable core work · 2–3 hours- Name who is responsible for keeping the standard current
- Agree how a change to the process gets proposed
- Store all standards in one shared location
Outcome: The process survives without you maintaining it · Someone other than you has updated a standard
Week
11
Confirm capacity improved
Priority 1 · Capacity bottleneck · 1–3 hours- Re-measure wait times for a week
- Compare with the baseline
- Name the next constraint
Outcome: Proven capacity improvement · Wait time is lower than the baseline
Week
12
Review, measure and plan what comes next
All three priorities · 2–4 hours- Review all three priorities and record what actually moved
- Write down the biggest win and the most important lesson
- Update your success scorecard with real results
- Decide the single priority to carry into the next 90 days
Outcome: A documented quarter and a clear starting point for the next one · Your scorecard reflects real results, not targets
AI & automation
AI is not where your next 90 days should go
Recommendation: Not a current priority
- With an AI Readiness Score of 30, the improvements in this Roadmap will create more value in the next 90 days than any tool would.
- Introducing automation now would add cost and complexity on top of work that is still being defined.
- This is a sequencing judgement, not a permanent one. Your reassessment in 90 days will show whether the picture has changed.
Guardrails
- • Keep a person accountable for every output before it reaches a customer or a financial record.
- • Never paste customer, financial or contractual information into a tool you have not checked for data handling and retention.
Measurement
Your 90-day success scorecard
Targets are not achievements. Record your starting point now, and fill in the result column on or after Day 90 with what actually happened.
Priority 1
Work moves through without queuing
By Day 90: The main constraint identified and its wait time measurably reduced.
Success looks like: The step that used to hold everything up no longer appears in your weekly problems.
Priority 2
Your core work runs the same way every time
By Day 90: Three core workflows documented, in use, and followed consistently.
Success looks like: Any job can be picked up mid-stream by another person without a conversation about what happens next.
Priority 3
Repetitive work takes measurably less time
By Day 90: Two repetitive tasks removed, simplified, or automated.
Success looks like: You can point at a specific task and say how many hours a week it used to take and how many it takes now.
Risk
What could derail this quarter
These are the specific risks your assessment surfaced — not generic warnings. Each one includes the early signal to watch for and what to do about it.
Moving the queue instead of removing it
Why we flagged it: Your responses show work backing up at a specific point, and the most common outcome of a quick fix is a new queue one step later.
What could happen: The original step looks better while total delivery time is unchanged.
What to do about it: Measure the whole path, not just the step you changed, before declaring the bottleneck cleared.
Early warning sign: The fixed step is fast but total delivery time has not moved.
Documentation that never leaves the folder
Why we flagged it: Your assessment shows core work is handled inconsistently, and the usual failure mode is writing processes that nobody then uses.
What could happen: You spend hours documenting, the team keeps working from memory, and nothing measurable changes by Day 90.
What to do about it: Use each standard on live work in the same week it is written, and edit it from real use rather than perfecting it first.
Early warning sign: A standard has existed for two weeks and has never been opened.
Automating a process that is not settled
Why we flagged it: Your assessment shows both heavy manual work and inconsistent process, and automating in that order tends to make the inconsistency permanent.
What could happen: You build an automation around one person's version of the task and spend more time maintaining exceptions than you saved.
What to do about it: Only automate a task after it has run the same way for two weeks, and always eliminate steps before adding tools.
Early warning sign: The new automation already needs a manual workaround.
Everything still routes through you
Why we flagged it: Your answers show high owner dependency, and a 90-day plan run entirely by the owner tends to stall in the busiest week.
What could happen: Roadmap work is the first thing dropped when delivery gets busy, and the quarter ends with insight but no change.
What to do about it: Give at least one priority a named owner other than you, and review it weekly rather than doing it yourself.
Early warning sign: Two consecutive weeks have passed with no Roadmap action completed.
Next steps
Start here, then keep going
Your single first move
Find where work waits longest
Complete by
January 19, 2026
Time required
≈2 hours
Supports
Priority 1 · Capacity bottleneck
Ninety days is long enough to change how Rivera Facility Services runs and short enough to stay focused. The businesses that get the most from this Roadmap are not the ones that do the most in Week 1 — they are the ones still working the plan in Week 9.
Reassess on or after April 12, 2026
Retaking the Fabstone Business Assessment™ after 90 days produces an updated Business Health Score and shows exactly which categories moved. It is the cleanest measure of whether this quarter worked.
If you want support executing this
A Fabstone Strategy Session™ works through your priorities with you, and AI & Operations Implementation™ puts our team alongside yours to build the systems this Roadmap calls for.
Roadmap FS-RM-SAMPLE · Prepared for Rivera Facility Services · January 12, 2026 – April 12, 2026 · © 2026 Fabstone Solutions LLC. Confidential.