Your business, out of your head and into a system.
Large companies hire architects to map how the business works. Simplified EA gives every business that map — people, capability, process and tools — in a few hours, in plain English. Then it keeps the map honest: it warns you about the gaps and reminds you before anything goes out of date.
Most businesses run on one person’s memory
Every business already has an architecture: who does the work, what the business is good at, how the work flows, and what it pays for. A large company draws it, owns it and keeps it current with a team of specialists. A small business keeps it in a head.
Meet Meena — nine years at a ten-person bakery, and the answer to almost every question. What did we promise the Sharma wedding? Ask Meena. Who covers the counter on Saturday? Ask Meena. It works, until Meena takes a month off.
And it carries a quieter cost long before then: nothing in a head can be searched, shared, measured or handed to a tool. AI can read a system. It cannot read Meena.
Enterprise architecture was built for enterprises
The discipline has always been worth having. It has just never been within reach of a business without a specialist.
| Traditional EA | Simplified EA | |
|---|---|---|
| Who does the work | A team of architects and a review board | You and your team, in a few hours |
| First useful answer | 12–18 months | A few hours |
| Language | Viewpoints, value streams, building blocks | Promises, people, jobs and bills |
| Staying current | A yearly project — charts go stale in between | Reminders before anything goes stale |
| What it costs | Licences, consultants, training | Priced per business — no specialist needed |
| What you end up with | A set of drawings | A living system that warns, reminds and scores itself |
Every architecture begins with four pillars
Strip away the frameworks and every enterprise architecture rests on the same four things — in this order.
- 1
People who
Who does each job — drawn from your staff list, with skills and cover, so the jobs resting on one person are named before a resignation names them.
- 2
Capability what
What the business does — the things you must be good at to keep your promises: taking orders, baking, delivering, buying.
- 3
Process how
How each capability is done, step by step, in your own words. A promise with no steps behind it shows up as exactly that.
- 4
Tools with what
What you pay for, and which work each tool serves — so the app nobody uses, and its renewal date, have nowhere to hide.
Capability is the what; process is the how. “We bake” is a capability. “Mix at five, prove for two hours, bake at 180°, cool on the rack” is a process. Keeping the two apart is the single most useful idea in enterprise architecture — and the easiest one to lose.
A business runs long before IT arrives
Picture a business with no IT at all. It still runs, because its foundations aren’t technical. People come first. Then the metrics and the data — orders in a notebook, prices in a ledger, who owes what. Then the process — how the work gets done, from opening to close. For most of history, every business ran exactly this way.
When IT systems arrive, they change one thing: they give all of that a home. The data gets somewhere to be stored. The process gets a workflow that operates it. The numbers are processed instead of recalculated by hand. And results come out the other side — reports, reminders, answers.
IT is not the business. It is the house the business moves into — and you should know the business before you build the house.
Enterprise architecture walks in on its own
Say it that way and the discipline appears by itself. A business vision calls for a business architecture — the people, capabilities and processes that deliver it. The notebook and the ledger become an information architecture — what you keep, and what it means. And the home becomes the technology architecture — the systems that store, operate and process.
Most small businesses meet this ladder upside down: they buy technology first and discover the architecture later, usually as a bill for an app nobody uses. Simplified EA walks it in the right order — top down, in plain words — so every tool has a reason, and every reason has a promise above it.
A loop you run, not a project you fund
Traditional architecture is a project with an end date, after which the drawings quietly age. Simplified EA is a loop: every pass leaves the map a little truer, and the health score shows you exactly how much.
- 1
Fill it in
Type your website address and the system drafts who you are. A few questions in plain English build the map; your staff list and app list fill in the names and the bills.
- 2
See the gaps
The system reads the map and writes the warnings for you: jobs that rest on one person, promises with no process behind them, tools that nothing uses.
- 3
Fix and plan
Every warning names one thing to do, with a one-click fix. Plans for the year tie to the promise they serve, and a moved date keeps the original beside it.
- 4
Keep it fresh
Every record carries a check-by date. Its owner is nudged a month before; the score drops if anything ages past it — so a stale map can never look healthy.
From your web address to a working map
Each step leaves something useful behind, even if the next one waits a month.
Type in your website
A first draft of your business page, from what you already say in public.
Answer a few questions
In plain English: promises, capabilities, one job end to end, who does what, what you pay for. The last screen shows the first warnings.
Upload your staff list
A payroll or HR export is enough. Jobs fill with names; one-person risks appear.
List what you pay for
Apps and subscriptions, tied to the work that uses them — and the renewals coming up.
Let the reminders run
Nudges before anything goes stale, a short digest of what moved, and the next step up the score.
Warnings in plain words — each with one thing to do
You never write a warning. The system reads the map and writes them for you, points at the record each one concerns, and tells you what acting on it is worth.
Taking orders depends on Meena alone.
You promise same-day local delivery, but no process delivers it.
Shift planner renews in 41 days — and no job uses it.
The food-safety inspection is due in 30 days. Arun owns it.
From “ask Meena” to “ask the map”
Every person-dependent business has a list of questions like these. Once the business is in the system, each answer has a home.
Fewer surprises. Decisions that don’t depend on memory.
See one-person risks early
“Invoicing depends on Priya alone” — named before a resignation or a sick week turns it into a crisis.
Stop paying for what nobody uses
Every tool is tied to the work it serves. Before a contract renews, you know what would break if you let it lapse.
Give every promise an engine
A promise with nothing behind it is flagged. Plans tie to promises, and slipped dates show up as facts, not feelings.
Survive a departure
When someone leaves, the business doesn’t have to relearn itself. The jobs, the steps and the reasons are in the system, dated.
Show outsiders a true picture
A bank, a buyer, an inspector or a partner sees a current, dated map of how you run — not a deck built the night before.
Be ready for AI
AI can only work from what is written down. Once your business is in the system, AI works on your real promises, people and spend.
Six promises the system keeps
You can’t type a good score.
The warnings and the health score are calculated from the map itself. Nobody can make it look healthier than it is.
Everything reads as a sentence.
“Taking orders depends on Meena alone.” No symbols, no notation, nothing to learn.
Every warning names one thing to do.
It points at the record it concerns and offers the fix.
Nothing is invented.
If your website or staff list doesn’t say it, the field stays blank and says so. Imports are suggestions until you accept them.
Everything carries a date.
You choose how often records are checked, from monthly to yearly. Everyone is held to the same clock.
AI drafts; you decide.
Where AI helps — reading your website, drafting your first map — nothing it writes enters the map until you say yes.
A finite architecture, for every business
Our Seventh Sense strives for optimal consumption out of a well-balanced capacity. For a business, that starts with knowing exactly what it has — who does what, what it does, how, and with which tools: a map with edges. Simplified EA draws those edges, so capacity can be balanced and nothing is consumed without a right need.
The map of your business
Promises and the four pillars, the warnings, the plan for the year, the staff list and skills, and the health score — with website and staff-list imports.
Software & subscriptions
Every app with a named owner, every contract counting down to its cancel-by date, who actually uses what — and the next bill forecast ninety days early.
Suppliers & the money
Renewals, equipment, supplier risk and spend against budget for each part of the business — reading the same contracts as Part 2, so nothing is typed twice.
Built for the business that never had a specialist
A bakery whose orders depend on one person. A plumbing firm with four vans and thirty subscriptions nobody has listed. A dental clinic where only the practice manager knows the suppliers. A tuition centre run by volunteers. A charity whose plan lives in its founder’s head. Each already has a way of working — it has simply never been written down where a system could hold it.
Your data stays yours
Your map belongs to you alone. Support staff can look but not touch, never see your costs, and nothing you record is used to build anyone else’s map.
See it on your own business
Send us your website address. We’ll build a walk-through from your public site — your promises, your capabilities and the jobs your team page names — with no invented person, cost or tool.
The bakery, Meena, Arun, Devi, Joseph and Priya are an illustrative example, not a customer.