Technical.ly Builders · May 8, 2026 · Philadelphia

Business OS. Every surface a solo
business needs.

How scattered business data becomes a knowledge system that compounds — markdown, vanilla JS, and AI.

Luis Cielak

buss-os.luiscielak.com

Business OS Demo buss-os.luiscielak.com
The Problem

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.

The Default

Knowledge that doesn't compound

Tool 1

CRM

  • Contacts
  • Deals
  • Notes
Tool 2

Spreadsheets

  • Finance
  • Pipeline
  • Planning
Tool 3

Docs / Notion

  • Strategy
  • Brand
  • SOPs

Each tool does its job. None of them talk to each other. Every decision costs you a search.

The Reframe
You don't need more tools.
You need a layer that makes
your tools compound.
The System

The 3-Layer Model

Three stacked planes: raw inputs as scattered shapes, a middle grid of organized knowledge, and top-level dashboards for decisions.
Inputs feed knowledge. Knowledge powers decisions.
Layer 1

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
Three-layer diagram emphasizing raw inputs at the base.
Markdown and files in inputs/ — home for Layer 1
Layer 2

Knowledge

Markdown as source of truth. Compile, don't copy.

inputs/90-day-plan.md → Quarterly plan + milestones → node skills/sync-plan.js → planning.html
Blueprint-style pipeline: planning markdown flows through sync tooling into compiled portal data and a static planning page.
One compile path — many input files
  • 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.
  • One pattern — every page.
Layer 3

Insights & decisions

Decision-grade views you open when you're about to act.

View 1

Dashboard

  • Revenue MTD
  • Active accounts
  • Top SKU
View 2

Pipeline

  • Accounts by status
  • Last contact
  • SKUs carried
View 3

Finance

  • Revenue by run
  • Pricing emulator
  • Margin by SKU

The questions you actually open the portal for:

How much does it cost me to run my business per day?

Case Study

Before & after

Same pattern as buss-os.luiscielak.com — shown here with YCC as the workshop-sized demo.

Before

Strategy in a doc updated twice a year. Pipeline in a spreadsheet. Finances in another tool. Notes in a folder nobody reopens.

Overhead flat-lay of a chaotic desk: overlapping browser windows, spreadsheets, sticky notes, and alerts — monochrome line art with a hint of teal.

After

One portal. One navigation. One design system. Pull up the view you need before the call — pipeline, finance, brand voice — and watch new inputs ripple through automatically.

Overhead flat-lay of one clean screen: structured portal with card grid and sidebar — matching companion illustration style.
Design System

One token file, every page

Palette × mode stay orthogonal — change a token and the whole portal moves together.

Grid of minimalist UI cards in light and dark rows across five brand-tinted columns, abstract placeholders only.
Light / dark rows × brand axes — no framework lock-in
Live Demo

Let me show you this on a real business.

Follow on phone demo-os.luiscielak.com

Yeast Coast Culture — fermentation & pickling; flagship product is a dehydrated sourdough starter.

01

Open YCC portal in browser — index.html → dashboard

02

Navigate to Planning — "this is Layer 3 — insights & decisions"

03

Open inputs/90-day-plan.md in Cursor — "this is a raw input, Layer 1"

04

Run node skills/sync-plan.js

05

Reload planning.html — new milestone appears — "this is Layer 2 doing its job"

Design Principles

Four rules that make it work

01

Markdown is the source of truth

Portable, diffable, AI-friendly.

02

Compile, don't copy

One edit propagates everywhere via sync scripts.

03

AI maintains; you direct

The model handles syncing; you own the decisions.

04

Own your infrastructure

No SaaS lock-in; everything in a git repo you control.

Abstract geometric composition: nested rectangles within a circle and radiating lines, Bauhaus-inspired.
Every exploration adds up — sessions feed back into the knowledge base instead of evaporating in chat.
Workshop Activity

Your turn — 4 minutes

My Scattered Inputs
  • What tools do you use?
  • Where does your roadmap live?
What Knowledge Lives Here?
  • What would your inputs/90-day-plan.md contain? (milestones, bets, owners)
  • What should the sync script output into portal/data?
What Decision-Grade View Do I Need?
  • What view changes your week?
  • What question do you answer every Monday?
What's next

Stay in touch.

Next: live workshop Cursor Philly · June 2026 cursorphilly.com

Luis Cielak · linkedin.com/in/cielak

Slides, demo, starter repo, worksheet — all here. buss-os.luiscielak.com