The outcome in one sentence. If it cannot be said, it is not ready.
02
Design
Draw it while it is still cheap. A page the team can argue against.
03
Plan
Cut it into tasks that fit a week, in an order that can actually run.
04
Execute
Build, review, ship. The plan is the receipt.
05
Standardize
What worked becomes a skill, so the next time nobody starts from zero.
one direction · no skipping
II
The tools
Four surfaces. Each one has a job the others do not do, and nothing gets stored in two of them.
Notion
the knowledge hub
Claude
the intelligence
Slack
the immediate
Claude Design
the brand
III
Information flow
Seven stations, one direction. Each one inherits the customer from the last.
◇
A conversation
A call, a thread, a note.
person
◐
Meeting
One row, with its customer.
agent
▦
Tasks
Drafted, waiting for a yes.
agentperson approves
◈
Project
Design, repo and channel.
person
⌘
Build
Branch, pull request, QA.
agent
◎
Review
Checked against the design.
person
↗
Launch
Merged, released, announced.
integration
The law underneath: the AI proposes, people decide. Every agent writes into a waiting state, never into a done one.
IV
Structured data, for analyzing after
Every database, its real properties, every link. The dark boxes are the spine.
the spinereaches outside Notionrelationsynced from GitHub⟲ points at itself
V
One source of truth
Every teamspace is a view of the same databases. Nothing is stored twice.
Nothing is stored twice. A teamspace filters the spine by its customer or its department, so the same task appears in the client's space, on the sprint board and in the KPI roll-up — as one row.
One HQ page. Every teamspace below it is a view of the same eight databases — never a copy.
12
✦ all crescō /HQShare···
crescō.
✦
HQ
Everything the team needs to build well, in one place.
→
New here? Open 00 · Start here and follow the path. It is the only thing you touch on day one.
Areas
Each area is a door. The eight databases are the spine — an area is a view of them, never a copy.
00
→
Start here
Onboarding, day one.
01
◐
Essence
Brand, voice, manifesto.
02
◇
How we work
Method, cadence, done.
03
⌘
Engineering
Stack, boilerplate, deploy.
04
◈
Customers
One teamspace each.
05
◎
Team
Who is who.
06
∑
Numbers
KPIs and finance.
07
▦
Master sources
The eight databases.
1Internal teamspaces first, customers second. A customer teamspace is where the client's work is read, not where it is stored. 2Eight cards, eight doors. Adding a ninth means adding a view, not a database.
One paragraph of what this is, written once, read by everyone who opens the row.
Tasks
Live view of the Tasks database, filtered to this project.
TableBoardTimeline18
TaskIDStatusSprintAssignee
◆Offline queue for the capture screenTSK-581PR OpenW-31LLuis
◆Retry flags on the local tableTSK-584RunningW-31LLuis
◇Last-sync indicator in the adminTSK-590QueuedW-32AAna
1Three plain URL properties. No integration needed, and they answer the three questions a project gets asked. 2The tasks are not a copy — it is the Tasks database, filtered.
The agent drafted. Nothing moves until someone presses a button.
12
▦ Tasks /Meeting task triageFilterSort···
Meeting task triage
Status is Refining · 5 waiting
TableBy meetingBy customer5
TaskTypeCustomerFrom meeting
◆Split the upload queue in twoTaskCustomer AScope reviewApproveReject
◈Customer portal, phase twoResearchCustomer AKickoffConvert into Project
◆Distribution flow without the app storeTaskCustomer AScope reviewApproveReject
◇Price the sync engine and the storage tierResearchCustomer BWeekly · Customer BApproveReject
◆Legal review before moving personal dataTaskCustomer BWeekly · Customer BApproveReject
1Written by the meeting agent — type, customer and source meeting already filled. 2Approve queues it. Reject archives it, never deletes it. Convert turns it into a project.
Same rows, counted. Per person, per sprint, per team — all of it rolled up from Tasks, so it is never out of date.
12
∑ kpis /DeliverySprint W-31···
Delivery
Rolled up from Tasks. Nothing is entered by hand.
By personBy sprintBy teamBy customerthis sprint
PersonLoadDoneOpenOn timeProgress
AAna1811792%61%
LLuis2214888%64%
MMara125771%42%
By personBy sprintBy teamBy customerlast 4
SprintPlannedDoneCarried overSPICPI
◷W-31 · current5230—1.040.98
◷W-30484441.020.91
◷W-295039110.871.05
1Four tabs, one database. Person, sprint, team and customer are just groupings of the same rows. 2SPI and CPI already live on Tasks as formulas over Load, Planned Value and Actual Effort — the roll-up only has to average them.
XI
Automations and skills
A skill is written once. After that the work never gets done by hand again — it either gets called, or it fires on its own.
⌘
Called
You type its name. It already knows the bases, the conventions and where the output belongs.
◷
Scheduled
A routine on a clock. It runs whether or not anyone remembered it was Monday.
⌁
Triggered
An event fires it: a meeting ends, a pull request merges, a row changes state.
whenroutinewhat it leaves behindlands in
◷ every morningmi-díayour day in order, before you open anythingSlack
◷ mondaymi-semanathe week measured against the sprintSlackNotion
◷ when a meeting endsmeeting-processorthe note, and its tasks waiting in RefiningNotion
◷ when a PR mergesrelease-notesthe release written in the studio voiceSlackNotion
◷ nightlyportal-auditorwhat the client can see, and what is missingSlack
◷ weeklykpi-rollupthe numbers closed, per person and per sprintNotion
The loop is the point: it runs again next week without anyone scheduling it twice, and it lands where people already are instead of in a page somebody has to remember to open. Some already run on their own; the rest are one cron away.
XII
Staying current
Four sources, one hour a week, one place it lands. A studio that builds with new tools goes stale in months, so this is a standing slot — not something we do when there is time.
The test for a trend is whether it produced a row. Everything else was entertainment.
crescō · notion & internal tools · v1.4drawn from the live schema