YOUR BUSINESS WORKS.

Until too much of it lives in your head.

Pharos Operations helps owner-run businesses create enough visibility and structure that the business becomes easier to run. The goal is not more software. It is reducing the mental load of keeping everything moving.

Start Discovery See how it works
Observation
Most owner-run businesses already know what to do.
The difficulty is holding operations, follow ups, projects, decisions, and information together without carrying all of it mentally.
Reducing that load is the whole point.

Most businesses do not have a software problem

They usually have a visibility problem.

Information exists
It is simply spread across too many places.
People know what is happening
But only individually rather than collectively.
Work still gets delivered
But coordination quietly becomes harder over time.
The point where people usually reach out:

"Nothing is broken. It just suddenly became harder to keep track of everything."

That is often where discovery starts.

What the service actually does

Rather than beginning with a tool, the process starts by understanding how work currently moves through the business and where friction appears. Practical operating principles are developed from that understanding, and a practical system is built around them.

Understand

Capture how work currently happens and identify recurring bottlenecks.

Translate

Turn observations into practical operating principles that guide day-to-day decisions.

Implement

Introduce lightweight structure that people can actually use from day one.

How We Work

The work moves from understanding to structure, then into practical implementation. Each step is there to reduce friction, not add ceremony.

01

Operational Discovery

Understand how work actually happens.

Map the real flow of work: enquiries, quotes, jobs, decisions, handoffs, exceptions, and follow ups. The aim is to see the business clearly before trying to improve it.

Output: a plain-language discovery summary.
02

Operational Governance

Define ownership, rules, decision points, and operating principles.

Decide what needs to be visible, who owns what, where decisions happen, and which rules should guide day-to-day work. This keeps the system grounded before any tooling is shaped.

Output: a focused tailoring brief.
03

System Tailoring

Fit tools to the business instead of forcing the business to fit the tools.

Shape a lightweight operating setup around the way the business already works. The goal is better visibility and smoother decisions without forcing people into an unnatural process.

Output: a practical system design.
04

Implementation

Introduce lightweight structure and visibility.

Put the agreed structure in place, test it against real work, and refine only where use shows it is needed. The standard is simple: it should make operations easier to carry.

Output: an operating environment people can actually use.

What you get

Practical pieces shaped around how the business already runs, backed by written rules so the system stays consistent.

A shared tracker

One place for jobs, quotes and follow-ups, so what is active, waiting and next is visible to everyone.

Automatic reminders

Prompts that fire on their own when something is waiting, so follow-ups stop depending on memory.

A daily view

One view of what needs attention today, instead of piecing it together from inboxes and messages.

Written operating rules

A short document that sets out who owns what and how decisions are made.

Built in whichever tool fits: Airtable, SmartSuite, n8n or Excel.

Common Friction Patterns

These are usually small, familiar patterns. Left alone, they increase the amount of attention needed to keep the business moving.

Work lives in inboxes

Symptom
Important details sit inside email threads, messages, and memory.
Hidden cost
Follow ups depend on whoever last saw the message.
Outcome
A shared place to see what is active, waiting, and next.

The owner becomes the bottleneck

Symptom
Small decisions queue behind one person because context is not visible.
Hidden cost
Work slows down even when the team is capable.
Outcome
Clear ownership and decision points that reduce checking in.

Spreadsheets require tribal knowledge

Symptom
The file works, but only a few people know how to read it.
Hidden cost
Errors hide in plain sight and handovers become fragile.
Outcome
Information that is easier to understand and safer to maintain.

Clients disappear after quoting

Symptom
Quotes go out, then follow up depends on memory or spare time.
Hidden cost
Good opportunities quietly drift without a clear next step.
Outcome
A simple view of who needs a response and when.

Nobody knows job status

Symptom
Status updates are spread across calls, notes, and informal checks.
Hidden cost
People spend time asking for updates instead of moving work forward.
Outcome
Reliable visibility into what is waiting, blocked, or complete.

Decisions happen in WhatsApp

Symptom
Important choices are made quickly, then become hard to trace later.
Hidden cost
The team loses the reason behind the decision.
Outcome
Clear decisions that stay connected to the work they affect.

Before / After

The shift is usually modest but meaningful: less chasing, more shared context, and fewer decisions carried alone.

Before

  • Chasing updates across messages and memory.
  • Reactive decisions because context is hard to see.
  • Duplicated admin in more than one place.
  • Uncertainty about ownership, status, and next steps.

After

  • Visibility into the work that needs attention.
  • Clearer ownership and fewer unnecessary check-ins.
  • More confidence in day-to-day decisions.
  • Smoother handoffs between people, jobs, and stages.

Who this is for

Businesses where one person is carrying most of the operational picture mentally.

Trades and installation businesses

You have three jobs moving at once, a quote you haven't followed up, and a supplier you're waiting on. You're holding all of it mentally because there's nowhere else for it to live.

Creative and design-led businesses

Your client work is excellent. The back-end of running it (enquiries, approvals, follow ups, delivery tracking) is getting harder to manage as the business grows.

Project-based service businesses

You coordinate projects, clients, and suppliers across a week that looks different every time. Nothing is broken. It just requires more mental energy than it should.

Work

Two examples of the approach in practice: rules agreed first, then a system built to enforce them.

Precision manufacturing, built in Excel/VBA

Procurement governance and reorder system

A mould-based manufacturer managed procurement through a legacy Excel/VBA workbook. The rules were agreed on paper first, then enforced by a three-tab system built inside the client's existing Excel environment.

  • 3 leads, 3 processes. The founder, floor supervisor and original file developer each described a different way to track and reorder stock.
  • Over 35% of active stock lines had no reorder threshold, so items could run out with no warning.
  • Double-ordering removed. Reorder logic now nets off stock already in transit.
  • 5,000+ formulas independently verified, with no new software or subscriptions.
Rook & Stammers, built in Airtable

Operating system for a bespoke framing business

Every order is a unique physical job with several suppliers and several pairs of hands involved. Rules such as no production before the deposit lands, and every job having a named owner, are built in as gates and exception views instead of being left to memory.

  • Deposit gate. Production tasks cannot start until the deposit is marked paid.
  • Margin per job is calculated from linked supplier costs before cutting begins.
  • Tasks created automatically at each stage, from supplier brief to installation prep.
  • 10 linked tables and 6 role-based workspaces.

Full case studies are available on request.

For agencies and consultancies

If your clients need operational systems built and your team lacks capacity, I take on the build white-label: Airtable or SmartSuite databases, n8n automations and workflow rules.

Email me the brief

Start discovery

Discovery starts with understanding how the business actually works, not selling a system. There is no lengthy intake process, just enough to understand whether this is the right fit.

Email me Message on LinkedIn
Email
luke@pharosoperations.com

No lengthy sales process.

What happens after you reach out

You'll receive a short set of discovery prompts. Most clients record a brief video responding to them, which takes around 15 minutes and can be done whenever suits you. From there, a practical tailoring brief is prepared before recommendations are made. No meeting required unless you would prefer one.

A note on timing. Pharos intentionally works with a small number of businesses at a time to keep the process thoughtful and tailored.

About

I founded Rook & Stammers, a bespoke picture framing business in Cape Town. From the beginning, I ran into the same problem most owner-operators do: the work was happening, but too much of how it was managed lived in my head.

I started documenting how work actually moved through the business, where decisions were being made, and where too much depended on memory. The resulting operating system made the business significantly easier to run.

As I worked with more businesses, I kept seeing the same operational patterns show up, regardless of trade or size. That recurring pattern, more than any single business, is what shaped this approach.

Pharos is the result. The service is informed by having lived the problem rather than diagnosed it from a distance.

How this gets built

The tool is chosen last, not first. Every engagement starts by working out how the business actually operates and what rules should govern it, before anything is built in Airtable, SmartSuite, n8n or Excel, whichever genuinely fits. A system is only finished once the people using it every day prefer it to whatever they did before. Technical completion on its own is not enough.

Small print
This website does not currently use analytics, advertising trackers, or cookies beyond what may be technically required by your hosting provider. If you contact Pharos by email or LinkedIn, your details are only used to respond to your enquiry and are not shared or sold.