The Art of Business · Chapter I

Chapter I: Foundations

Guides · Art of Business · By Marcus Covington

Founder handbookChapter IMarcus Covington

← Preface · Series index

The builder and the banners

A builder showed up in a trading town with a plan for a big house. He hired painters first. They covered the square with banners: towers, gardens, a gate wide enough for a parade. Merchants nodded. Workers gathered. The builder started calling himself master of the district.

An older mason asked where the water would drain.

The builder pointed at the tallest tower in the picture. The mason asked again. No trench. No survey. Under the courtyard ran a stream that rose every spring.

Across the square, another builder rented a small shop. She surveyed the ground, laid drainage, and locked in stone suppliers. Her walls went up slow. When the rains came, her shop stayed open. She fixed the first builder's flooded storeroom and bought the lot next door.

The banners lasted until the wind changed. The drains lasted for generations.

Every founder keeps choosing where the next hour and the next dollar go. Appearance versus load-bearing work shows up in a hundred costumes. Learn to feel the weight a decision will have to carry.

Contested markets, quiet contests

Business fights often finish before the public notices. A better distribution deal changes who reaches the customer. An operating fix changes who can serve that customer at a profit. A reliable team buys one company time another spends recovering from preventable failure.

Markets are contested ground. Capital, technology, distribution, trust, ownership, and the ability to deliver all matter. Your spot on that map shapes your options. Lean on one middleman and you have less freedom than the revenue line suggests. Hold direct customer relationships and operating knowledge other people can use, and you may be stronger than your size looks.

Useful categories still help: who can run, recover, and replace an essential service; whether your public story matches what you actually deliver; whether rights and obligations are real in the jurisdiction that counts. Treat them as evidence problems, not slogans.

The most expensive opposition often starts inside. A confused process wastes effort every time it runs. Wounded pride can redirect weeks of work. A shaky partner turns capacity into dependency. A legacy procedure outlives the reason it existed.

Look inward first. Know what you actually control before you talk about what you plan to take.

Structure, leverage, advantage

Three pillars.

Structure is how decisions become action. Ownership, authority, records, continuity. Without it, progress hangs on memory and whoever is online. Keep it simple. One honest ledger, one accountable owner, and one clear escalation rule can beat an org chart nobody follows.

Leverage is effort that multiplies. A reusable procedure, a distribution relationship, a trained manager, a tool that works. Leverage also multiplies mistakes. A bad automation rule repeats an error faster than any person could. Apply leverage to work whose purpose and limits you understand.

Advantage is making it increasingly reasonable for customers to choose you. Not aggression theater. Not "inevitability" as destiny. No market outcome is guaranteed. You earn durable edge by value, reliability, and a lower cost of picking you. Claiming inevitable success does not move demand.

Ask three questions. Can we act coherently? Can we get more value from what we have? Can we keep an advantage customers care about? Growth that weakens all three is expansion without a foundation.

Command of self and vision

You are the first command system. Your attention decides which signals get action. Your habits train how the company reports bad news. Your tolerance for unfinished work becomes everyone else's operating condition.

Separate the event from the decision it requires. A competitor announcement may need investigation, a pricing look, or nothing. An angry message may hide a real service failure. Personal offense and business consequence can both be true; only the business consequence should spend company resources.

Keep a decision record for material commitments. Objective, known facts, the assumption doing the most work, the downside, and when you reverse. That kills mood-driven decisions and makes learning possible. Without a record, people remember the confidence and forget the uncertainty they ignored.

Vision needs a direction with edges. "Build a great company" does not settle a Monday conflict. "Make managed service reliable enough for small retailers to run without a tech staff" tells you what to build, who to hire, how to price, and what support looks like. It also kills shiny distractions.

You can hold a wide destination and run a narrow campaign. Destination for continuity. Campaign for focus. Mix them up and you get early complexity: too many brands, markets, and operating systems, and no single offer strong enough to fund the rest.

Resources and the work nobody sees

List resources at usable value. Cash promised next month does not pay a bill due today. A server with no customers is capacity with a cost. A talented acquaintance with no commitment is a maybe. A procedure only one person knows is a single point of failure wearing a smile.

Public promises rest on work customers rarely see: account recovery, supplier terms, documentation, backups, renewals, access control. Treat those as clerical details beneath your interest and the company gets brittle.

Call that supporting layer what it is: the work outside the spotlight. Keep it orderly so delivery and continuity hold. Hiding things so authorized people cannot operate is just another dependency. Privacy and accountability can live together when access follows responsibility and actions leave records.

Picture a hosting company with three paying customers and twelve product lines. The founder wants a second region. First he lists why customers buy, how much time serving them takes, and what cash is already committed. They care about managed recovery and fast help more than a bigger map. He improves that service, writes the procedure, and hands routine requests to another operator. Strength without buying another machine.

Same idea for a publisher, a manufacturer, or a local service firm. Foundation work removes the constraint that actually blocks productive growth.

Make the declaration operational

"I will build something that moves with my judgment" sounds grand. The real burden is concrete. Know your materials. Respect load. Account for the people who will live with what you build. Ambition does not overrule the economics of a service.

Write a one-page charter. Who you serve. The problem you solve. The advantage you intend to build. The obligations you protect. Which decisions you keep and which others can make. The single constraint whose removal would most improve the next ninety days.

Then look at last week's spend and attention. If the charter and the calendar describe different companies, trust the calendar. Change it on purpose.

Field order. Produce an asset register, an authority map, and a short list of current promises. Pick one weakness that threatens those promises. Fix it before you authorize a new campaign. You have enough foundation when the organization can explain what it owns, what it owes, who decides, and how the next important result gets delivered.

Related

← Preface · Series index

How we run GlassHosting

This handbook is the doctrine behind how I build. GlassHosting operates with MSP discipline on what we run today — including Glass Gaming Soft Launch. No invented uptime badges. No fake global maps. Read the MSP posture.

MSP standards Glass Gaming All guides