Internal tools for firms whose engineers are busy
The customer of a small Austin software company has just signed, and wants to know when its team will be live. Behind that question sit setup steps, each belonging to somebody: accounts to create, data to bring across, people to train. Later the same customer wants fair notice before the contract renews. A partner who resells the product wants to register a deal and know it was seen. None of them sees how the firm keeps track until a step is missed.
Inside the firm, every developer is on the product. Austin has no shortage of people who can write software; what its firms lack is spare engineering time, so the tool the operations team asked for waits another quarter. Until then setup lives in a spreadsheet, the renewal date in someone's calendar and the partner's request in an inbox. What we build replaces those: a board of each new customer's setup steps and their owners, a list of contracts by renewal date with the notice period, and a form partners use to register a deal. The operations lead decides when a customer is marked live, and a step with no owner is shown as such, not assigned by the software. A technical consultancy has the same gap, with engagements in place of accounts. We build to the firm's conventions so its engineers can take the tool over. Scope and price are fixed in a brief before building starts.
Then a message arrives from a company in London that nobody at the firm has met. It heard of the product from a customer in New York and asks what setup involves and who would look after it. Run from spreadsheets, that message would wait for a free hour. Here it is logged on the board, and from signature onward its steps, owners and renewal date sit on the board beside those of the Dallas accounts. The operations lead answers from what the board shows, and no engineer leaves the product to find out. Nobody has flown to London, and the firm has added no operations hire for the account.



