Module 15 · Lesson 03

The 90-Day Engagement Model — What We Promise and What We Deliver

Reading time: 14 minutes Track: Yungsten Tech Employee Curriculum · Required for all staff

The engagement architecture

A full Yungsten engagement is built around a predictable rhythm: biweekly 90-minute sessions with the C-suite, a quiet wiki tended between visits, four named agents built over the first quarter, and a monthly seminar for the broader team.

This structure is intentional. Consistency beats intensity. A predictable rhythm builds trust, surfaces problems early, and creates the accountability that makes execution happen between sessions.

Phase 1: Orientation (Weeks 1-2)

What happens:

• Deep intake with C-suite
• Audit of existing AI tools, prototypes, and workflows
• Data classification assessment
• Wiki foundation: initial structure, first entries covering the organization's context and the engagement scope
• Agent 1 scoped and development begun

What the client experiences:

• Clarity on where they are vs. where they think they are
• A written plan for the quarter
• A wiki that already has useful content about their organization

What we need from them:

• Access to existing tools and prototypes
• 3-4 hours of C-suite time for the initial sessions
• Clear ownership of the engagement on their side

Phase 2: First Delivery (Weeks 3-8)

What happens:

• Agent 1 delivered and in use
• Agent 2 scoped and built
• Wiki expands to cover the first agent, organizational processes it supports, and initial prompt patterns
• First monthly seminar for the team
• Biweekly sessions continue — adjusting based on what's actually working

What the client experiences:

• Real AI tooling in use by the team, not just in development
• First seminar creates broader team buy-in
• Wiki starting to be referenced organically

Phase 3: Compound Value (Weeks 9-12)

What happens:

• Agents 3 and 4 built
• Wiki reaches self-sustaining depth — client team can add to it themselves
• Final monthly seminar covers team-level AI conventions
• End-of-quarter review: what worked, what's next

What the client experiences:

• Four operational agents their team uses daily
• A wiki that works without Yungsten maintaining it
• A team that can onboard new members to their AI stack

Setting client expectations

The hardest expectation to set: results compound, they don't spike.

Clients often expect dramatic transformation in the first two weeks. The reality: the first month is mostly infrastructure and trust-building. Weeks 3-6 show the first real results. Weeks 7-12 are where the compound value becomes visible.

Set this expectation explicitly in Week 1: "By Week 12, your team will have four operational agents, a self-sustaining wiki, and the habits to keep building. The first month will feel slower than you expect — that's normal and necessary."

Clients who expect a spike and get compounding often feel disappointed in Week 3 even when they're exactly on track. Clients who expect compounding stay engaged through the slower early phase.