Business
OS
How scattered business inputs become a structured knowledge system — built and maintained with Cursor.
Luis Cielak
luiscielak.com
How many places does your
business knowledge live?
Raise your hand if it's in more than 5 tools.
Keep it up if it's more than 10.
Knowledge that doesn't compound
CRM
- Contacts
- Deals
- Notes
Spreadsheets
- Finance
- Pipeline
- Planning
Docs / Notion
- Strategy
- Brand
- SOPs
Each tool does its job. None of them talk to each other. Every decision costs you a search.
You need a layer that makes
your tools compound.
The 3-Layer Model
Inputs
Raw business data from wherever it lives: CRM, finances, strategy, operations, marketing.
Knowledge
Markdown as source of truth. Compiled by sync scripts. Maintained by AI.
Decisions
Actionable views you open when you're about to act: pricing tools, pipeline, OKRs.
Inputs
The raw material. Everything your business already produces.
- CRM notes & deal history
- Financial reports & production-run data
- Strategy & planning docs
- Operations & SOPs
- Marketing copy & brand guidelines
Knowledge
Markdown as source of truth. Compile, don't copy.
- One file is the source. Everything else is compiled.
- AI maintains the structure. You direct the decisions.
- Git is your version history. Cursor is your editor.
Decisions
Actionable views. Open them when you're about to act.
Dashboard
- Revenue MTD
- Active accounts
- Top SKU
Pipeline
- Accounts by status
- Last contact
- SKUs carried
Finance
- Revenue by run
- Pricing emulator
- Margin by SKU
Before & after
Fragmented tools vs. one portal — abstracted here as consulting ops,
detailed at buss-os.luiscielak.com
Before
After
One token file, every page
Palette × mode stay orthogonal — change a token and the whole portal moves together.
Let me show you this on a
real business.
Yeast Coast Culture — fermentation & pickling; flagship product is a dehydrated sourdough starter.
Open YCC portal in browser — index.html → dashboard
Navigate to Pipeline — "this is what Layer 3 looks like"
Open session-notes.md in Cursor — "this is a raw input, Layer 1"
Run node skills/sync-session-notes.js
Reload pipeline.html — new account appears — "this is Layer 2 doing its job"
Four rules that make it work
Markdown is truth
One file is the source. Never maintain the same data in two places.
Compile, don't copy
Scripts transform your knowledge into views. Editing the view is a dead end.
AI maintains, you direct
Cursor writes the sync scripts and keeps the structure clean. You make the decisions.
Own your infrastructure
Files, git, static HTML. No SaaS lock-in. No subscription required to read your own data.
Your turn — 15 minutes
- What tools do you use?
- Where does your CRM live?
- Where does financial data live?
- Where does strategy live?
- –
- –
- What would a markdown file contain?
- What fields does it need?
- What would a sync script compile?
- –
- –
- –
- What question do you answer weekly?
- What view changes your week?
- Who else on your team needs it?
- –
- –
- –
Fork it. Build yours.
Case Study
buss-os.luiscielak.com
Starter Repo
github.com/luiscielak/
Community
Cursor Philly
Luis Cielak · luiscielak.com