Before Kitstak
The operation ran on a stack the founder describes as honest: a Slowbooks file for accounting, three spreadsheets for inventory tracking, a fourth for kit BOMs, an email folder for customer authorizations, and a manual cross-check at month-end that took two business days. The team trusted the numbers because they trusted the people. They did not trust the numbers because the database told them to.
Specific pain points the team named in onboarding:
- Three brand customers reported phantom shortages that turned out to be tab-sort errors.
- Month-end close drifted past the fifteenth of the following month before the controller intervened.
- Labor cost was a guess. Hours rolled up to the warehouse, not to the customer.
- Audit trail for inventory adjustments lived in three notebook pages and one Slack DM.
The implementation
The Kitstak implementation took five business days. Founder-led. The team's existing data migrated via CSV import. Day one was org provisioning, branding, and user invites. Day two through four imported customers, items, BOMs, and opening stock levels. Day five was the chart of accounts alignment and the cutover.
The cutover happened on a Monday morning. The team kept the Slowbooks file open as a fallback for ten days. They did not need it after day three.
What changed
Six weeks after cutover, the operation looked different at the database layer and at the office.
- Month-end close: from the fifteenth to the third business day. The chassis writes journal entries as you operate; the controller reconciles instead of building.
- Phantom shortages: zero. Stock levels are GENERATED columns; the database does not let them drift from movement history.
- Labor visibility: hours allocate to the customer, the run, and the task. The team can answer "which brand drove our labor variance last week" before the meeting starts.
- Cost-to-serve: KitCost surfaced two brand customers operating at negative margin. One was repriced and stayed. One was politely transitioned.
- Audit trail: every state change writes a hash-chained audit row. Inventory adjustments now have a who, when, and why on every line.
What did not change
The team is the same. The customers are the same. The warehouses are the same. The operation runs the way the operator runs operations. Kitstak did not impose a methodology; it ran the existing methodology cleaner.
The operator on Kitstak
We trusted the numbers because we trusted our people. Now we trust the numbers because the database tells us to. The team is the same. The discipline is finally legible.
The operator, customer zero