Building it ourselves so we could try to break it
My infrastructure partner handed me a blueprint, and I built it in house first so he could attack it.
My infrastructure partner showed up with a blueprint of the systems we would need next. Hiring it out or sitting through a proposal cycle was the obvious path. I told him instead that we would build the thing ourselves first, then give it back so he could try to break it.
In a matter of days a secrets manager was deployed, our project and CRM tools were up, and the full agent roster was under review. I called it, at the time, the biggest reboot we had attempted.
Here is my rule for any consultant's design, technical or not: build it yourself before the expert gets it. Waiting for a proposal, then waiting again for the build, buys weeks of learning nothing. Building first means you hold the knowledge no matter what the expert later criticizes, and the handoff turns into a true adversarial review instead of a formality. Moving fast shows you understood the design.
Story details
| Project | CRM Migration |
|---|---|
| Type | Strong opinion |
| Firm telling | on the Common Ground wiki |