Build it: playbooks
Step-by-step builds for the systems teams actually run — CRM, inventory, hiring, projects, content.
How to build a CRM you'll actually use
Most CRMs fail because they ask for more data than they give back. Here is a five-table model that stays useful, and the fields that earn their place.
Orders and line items: the classic build, done right
Every order system is the same three tables. Getting them right — especially the frozen price — is the difference between accurate revenue history and quiet corruption.
A project tracker that survives contact with a real project
Most project trackers die because updating them is work that benefits someone else. Here is a model where the person doing the update gets something back.
Build a content calendar that connects to the work
A calendar of dates is not a content system. Model pieces, channels and distribution separately and you get planning, production and performance in one place.
Build an applicant tracking system in an afternoon
Hiring is the textbook many-to-many problem. Model applications as their own table and the pipeline, the reporting and the candidate history all work.
Build an inventory system that reconciles itself
The single biggest inventory mistake is a stock level you edit by hand. Track movements instead and the number becomes both correct and explainable.
Collect work from clients without email ping-pong
Requests arriving by email are unstructured, unassigned and untracked. Structured intake fixes all three, and takes about an hour to build.
Track equipment and assets without a spreadsheet graveyard
Asset registers rot because they record state instead of events. Model custody and maintenance as movements and the register stays true on its own.
Stop fighting your spreadsheet
RowFold gives your data the structure it already has in your head — tables that know about each other, views that fit the work, and AI that can actually answer questions about it.