Seven years in, growing fast, and still running on a spreadsheet only one person could really operate.

The client, Rovic Agriventures Inc. (RAI), is a medium-sized egg production operator in the Philippines. Seven years old, family-adjacent, and disciplined about cash by design: no net terms for anyone. Customers pay on pickup, or they pay before the eggs leave the farm. That policy protects the cash position, but it also means every peso of receivable, every peso of expense, every peso of inventory is a live decision made in near real time.

Growth had made the business more complicated than the tools it inherited from its earlier stage could serve. New product streams, new customer segments, new operational commitments — all arriving faster than the workflow could absorb. When the tools that got you to the first plateau start to slow you down on the way to the next one, the fix is not more of the same. The fix is a new set of tools, designed for the shape the business is now becoming.

RAI was running the operational side of the business on a single Google Sheets workbook, and it worked. That has to be said honestly, because it is true. The difficulty was not that the workbook was broken; the difficulty was that the workbook was a person. Only the person who built it could really run it, and only she knew where the fragile links lived.

Every start-of-month and end-of-month, the team had to close one loop and open another, and that meant cell-linking, manual adjustments, and reconciliations spread across sales, expenses, collections, and cash flow. When the builder was on it, the close took a few hours; when anyone else touched it, the close could stretch across two days. That kind of variance is the tax you pay for a tool that only one person really understands, and RAI was paying it every month.

The deeper problem, though, was quieter: the data was there, but it wasn't being used. Nobody was interrogating it for pricing patterns, for seasonality, for payment behavior. There was no forecast, no strategic view, no clear read on which months were about to lean and which were about to peak. The business was making decisions based on the last month it had closed, when it should have been reading the next one it was walking into.

Studio JNSQ's first instinct on operating-system engagements is to ask what the shape of a working day actually looks like inside the business, and then design around that shape rather than around a database schema. In RAI's case, the working day begins in production, moves through sales and collection, becomes cash flow, and ends the week as receivables, expenses, and a customer view. So the system was built to run in that exact order, tab by tab, exactly the way the day flows.

The engagement was scoped generously — 60 days, with room for migration, forecasting, and additional features — because the client had already tried a faster version of this rebuild with someone else and it had not landed. We compressed the timeline aggressively, delivered in 21 days, and used the extra runway not to expand scope but to over-invest in three areas that determine whether a system like this actually gets used in daily operations: trust, speed, and forgiveness. Trust meant a privacy layer that the owner could rely on when showing the tool to lenders, investors, or auditors. Speed meant a data-entry pattern that removed duplicate encoding entirely. Forgiveness meant an autosave that never asks you to remember to save.

The data engineering was deliberate. Google Sheets is the backend, but the application layer treats it like a database: computed rows (crack percentage, production rate, production trend) are locked so an encoder cannot accidentally overwrite derived values. Inventory reconciliation runs continuously, comparing system counts against physical counts and surfacing the variance as a single number. Every sale auto-posts its unpaid balance to Accounts Receivable. Every collection auto-posts to Cash Flow with the correct bank position. The system does not ask the user to remember which ledger needs updating; it cascades the entry across every affected module in one save. On the analytics side, Chart.js renders five live charts on the dashboard alone: a year-end forecast with adjustable growth multiplier, year-over-year comparisons for good and crack production, and an expense breakdown by category. The Expenses tab adds its own analytics rail with spend-by-week and an unusual-expense detector that flags any title the system has never seen in prior months.

A growing operator does not need every number on one screen; she needs the right five, in the right order, updated the moment she opens the app. So the dashboard opens with a compressed KPI row that reads like a morning brief: revenue for the period, current cash holdings across all bank positions, current accounts receivable, current inventory value, and the two production averages that quietly govern everything else. Underneath that row sits the piece the client asked for most explicitly: a full-width, adjustable Year-End Forecast with a growth multiplier the owner can dial and re-apply live. The forecast uses Chart.js to render actuals as a solid line and projections as a dashed continuation, so the boundary between known and assumed is always visible.

Below the forecast, three comparison charts track production (good trays and crack trays, 2026 vs 2025, month over month) and an expense doughnut breaks spending by category. Every chart responds to the scope selector at the top: switch from YTD to MTD, and every tile, every chart, every subtotal re-scopes in one click. That scope control was a UI decision rooted in how the owner actually uses the tool: she checks the week on Monday, the month on the 1st, and the year on the 15th of June. One selector, one mental model.

Any founder who has ever pulled up a live dashboard in a lender meeting knows the fraction-of-a-second panic: who is going to see this next. So the RAI system carries a single, deliberate switch in the top bar labelled Hide $, and it does the exact opposite of what a normal toggle does. It defaults to visible, but the moment you hide the numbers, you cannot reveal them again without a password. That inversion is small, and it is intentional.

Before the engagement, the team was entering the same transaction as many as four times — once in sales, once in the collection tracker, once in the cash flow ledger, and once in the customer note. Every duplicate carried a risk of drift; every drift required reconciliation; every reconciliation stole time from decisions that actually mattered. The new system asks for only two inputs during a normal operating day: the sale, and the production. Everything else composes itself.

RAI runs across four cash positions — three institutional bank accounts and physical cash on hand. Before the system, knowing the current balance in each meant checking four different places at four different times of day. The new Cash Flow tab surfaces all four positions in a single card on the right side of the screen, always visible while the team edits records on the left. The records grid supports an inline edit mode that autosaves every two minutes and on tab switch, so nothing is ever lost in the middle of a conversation.

Most AR dashboards are built for businesses that expect receivables to sit for thirty, sixty, or ninety days. RAI is not that business. The company was built to be paid on pickup or before, so an aged receivable is not an accounting reality — it is a signal that something in the operating process broke down and needs to be addressed today, not next month.

When a customer shifts into amber, the operator sees it the same day; when a customer shifts into red, a phone call goes out that afternoon. That single change — the visibility of aging as a colour rather than a column of dates — is what turned collections from a reactive task into an operational discipline.

Owners of growing businesses ask the same question every month: what changed. Not the total; the total is a number they already have. The real question is where the total came from, and whether anything unusual was hiding in it. A traditional expense report puts that answer three or four exports away.

The reconciliation conversation with the owner used to take an hour; it now takes about six minutes. The owner asks what changed, and the tab has already answered.

When you replace a tool people have used for years, the migration cost is not the data — it is the muscle memory. So the Production tab keeps the exact same shape as the source workbook: month across the top, buildings down the side, days as rows underneath. The new element is the small weather widget in the top right and the free-form Notes column on the right that autosaves as the team types. Poultry production is weather-sensitive; that is not a business insight, that is physics.

The month-end close-loop is no longer a ritual. It happens automatically at the end of every month because there is no manual reconciliation to perform; the ledgers stayed in sync all along. The team's encoding time compressed once duplicate entry was removed. And for the first time, RAI enters each quarter with a forecast on payment behavior, on seasonality, on pricing, and on market movement — the kind of foresight a business needs when it is about to talk to a bank.

Post-launch, Studio JNSQ added a prepayment feature after watching the client experiment with pricing incentives to accelerate cash flow. The design was small: a discount toggle on the sales entry, an automatic write to the cash flow tab, a note on the customer card. The effect on client behavior was disproportionate. More customers now prepay than the team expected, and the composition of the receivables curve shifted in the direction the business wanted.

This is the moment where the Resource Value Formula™ makes itself visible. Not in the software; in what the software freed up. RAI is now preparing to onboard investors and is in active conversation with a bank partner for expansion capital. Both moves depend on the business being able to answer any question about its own numbers with confidence, and both moves are directly enabled by the confidence the new system gives management to speak to those numbers.

The resource we set out to recover was not money; it was attention. Management attention that had been going into monthly close-loops and manual reconciliations is now going into expansion planning, investor preparation, and the conversations that come with a bank at the table. That is the compounding effect the Resource Value Formula™ is designed to produce.