A CRM nobody had touched in years, shipping again in three months
We're three months in and still feel like we have lightning bolts coming out our fingers. Speed and quality usually are at odds, but not with Software Factory. Both are up and to the right.
Client
Sector
IT consulting
Time on platform
3 months
WeeksMinutes
time to iterate on a change
Red Oak built their CRM years ago and it had sat untouched since.
The code was there and most of the same developers were still on the team, but they had moved on to other projects and no longer remembered the detail of how it worked. Restarting the CRM meant rebuilding that understanding fast enough to accelerate Red Oak's go-to-market. Software Factory got them back in touch with what they had built, and they were rolling again almost immediately.
Before Software Factory, a product manager spent 30 hours making a Figma prototype and then translating it into tickets for engineers. Changing course midstream was expensive, and detail got lost between the original idea and the individual tickets. Engineers rarely saw the source documents behind the work they were handed. Now iteration takes minutes rather than weeks, and the engineers understand and remember what the team is trying to accomplish.
Red Oak has built a range of features on Software Factory.
These three are a workflow, an agent, and an architectural rewrite.
A · In-field photo verification templates
Built for a solar panel installation company. An office administrator creates a template of the pictures that need to be taken to verify work performed in the field. Financiers require verification via pictures. The feature gives structure to those requirements.
B · In-product review agent
An agent reviews a project inside the CRM and works out its status and next steps. It then drafts the email or pulls in the information it needs.
C · Multi-tenant conversion
The CRM Red Oak built for themselves is now multi-tenant across data, permissions, and users.
Are your teams still choosing between shipping fast and shipping well?
Software Factory keeps the intent attached to the work, so a team can pick up a system they have not touched in years and start shipping. Requirements captures that intent in plain English, and the Knowledge Graph carries it forward through Blueprints, Work Orders, and Feedback.