Aaron Claycomb Contact
Systems · Operating principles

The same instinct shows up in every case study.

Different surfaces — a portal, an email system, a narrative product, a giving cycle, a publication — but the operating logic underneath is the same. Six principles. Short enough to read, honest enough to argue with.

  1. 01

    Build the system the work actually needs — not the one the platform suggests.

    Platforms ship with a default grammar. The better the operator, the more they treat that grammar as a starting point, not a ceiling. Bluepathways was the clearest example: Slate was never sold as a portal; shaping it into one was the decision.

  2. 02

    Carry consistency in the infrastructure, not in individual vigilance.

    Brand drift is a structural problem. If the email system can produce an off-brand send, it will. The modular email architecture fixed that by refusing to give the drift somewhere to live.

  3. 03

    Make the system legible to the people using it.

    A dashboard that leadership can't read is worse than no dashboard. Slate reporting discipline is written to answer questions, not display data. Same principle in the applicant portal — visible status, visible next action.

  4. 04

    Govern what should be governed; free what should be free.

    Lock the shell, free the copy. Segmentation logic is mechanical; strategy is human. Most teams invert this and end up with rigid strategy and loose governance.

  5. 05

    Editorial is a structural asset, not a finishing touch.

    Voice decides whether the infrastructure is worth anything at the edges. A CRM that ships polished, tone-deaf copy is a CRM that ships. Editorial discipline is load-bearing.

  6. 06

    The work should compound after launch, not decay.

    Campaigns decay. Systems compound. The thirty-sixth time a giving-day cadence gets assembled, it should be faster, sharper, and smaller-risk than the first. That curve is the point.

Where this shows up

Read the case studies with the principles in mind.

Each featured study is a different surface — portal, email system, narrative, giving cycle, publication — running on the same operating logic. That's the through-line.

See the work →