Solution Architect

Growth systems
· Between the conversation and the build

You sit between what a founder says is broken and what a team can actually build, and you turn one into the other. What reaches the builders is a design, not a wish.

Most of the waste in this industry lives in the gap between the growth conversation and the build. This role sits in that gap on purpose.

• Turn what a founder says is broken into a system design: what's automated, what stays human, what the stack looks like when it works.
• Decide where AI genuinely belongs in a workflow and where a human has to stay.
• Write scopes the shipping team can inherit without a translation meeting.
• Work both sides of the gap: the growth conversation with the brand, and the build conversation with the engineers.
• Pressure-test every design against the stack and the data the brand actually has.
• Stay close to the build until the system is running as designed and being used.

The design. You turn what's broken into a system: what's automated, what stays human, what the stack looks like when it works, and a scope the shipping team can inherit without a translation meeting. When the build starts, the hard thinking is already done.

• You've been the engineer who resented the vague brief, or the strategist who watched a good idea die in the build. Probably both.
• You like being the person who makes the ambiguous thing concrete.
• You can hold a technical design and a founder conversation in the same day.

If you need to pick one side, pure architecture or pure client work, this role won't let you. It's the bridge, and the bridge gets walked on from both directions.

Whether the systems you scope get built as designed, get used, and move the number they were designed to move.

Not a resume. One thing you made or moved that speaks to this role. We read every one, and we write back either way.