The Closson Labs journal
How we’re building, what we’re learning, and why industry knowledge belongs at the center of software development.
Follow via RSSTwo foundations behind the products we’re developing
Forms that help people finish, records they can work through, and clear feedback when something changes. A detailed look at our shared interface foundation and why it matters to the people using it.
Read the article : A design system for the work people doAccounts, permissions, documents, search, background work, and useful intelligence. What we’re building into the common foundation, and what it lets each industry product focus on.
Read the article : The shared platform beneath an industry productProducts, partnerships, and the economics of software
Reusable foundations and better development tools change the economics of building. Our bet is that customers should benefit, while useful intelligence earns its place through the work it helps them finish.
Start with the workarounds, handoffs, and exceptions your team already understands. They can reveal the difference between a configuration problem, a custom tool, and a product opportunity.
What our platform and design system can carry forward, what remains specific to a business, and why ownership still needs a practical handover.
Real influence on the product, direct access to its engineers, and early use of working software. How your industry knowledge becomes part of the build.
How to distinguish a need for direction from a need for engineering capacity, and what a useful fractional CTO engagement should help a team decide.
Why our planned platform model combines a company base fee, unlimited users, and a shared usage allowance for hosting and intelligence.
New articles on the products, the decisions behind them, and what we learn along the way. Sent when we publish.