Statement of Work

Influence Scorecard — V1 Build to Production

Engagement Purpose

This engagement takes the existing Influence Scorecard demo at guacandroll.vercel.app and brings it to a production-ready V1 that Christian can begin testing with real clients. The work installs a real database, real AI-powered scoring built on Christian's proprietary framework, the dashboard and filing structure laid out in his Version Map, and the scorecard structure he designed.

This engagement covers V1 only. V2 (Coach and Admin dashboards, search, analytics, tags) and V3 (book ingestion, relationship intelligence) are explicitly future engagements, scoped separately if and when Christian wants to expand. The intent of this engagement is a working product Christian can put in front of real users, gather feedback, and validate before further investment.

Scope of Services

The engagement consists of four scheduled touchpoints across four weeks, plus async build work between sessions.

Async build work happens between sessions. Slack, Loom, or email used for in-flight questions and decisions that do not require a live session.

Deliverables

By the end of the 4-week engagement, Christian will have the following in hand:

1. A production V1 of the Influence Scorecard deployed on Christian's Vercel account at his chosen domain (current options: tools.thechristianhansen.com, influencescorecard.com, or another domain of his choice).
2. Real authentication and a real Supabase database with secured storage. Replaces the current localStorage demo. Christian owns the database and the user data inside it.
3. Real AI-powered scoring using Christian's proprietary scoring framework. The scoring runs through Christian's Anthropic API key (his usage, his bill), evaluates transcripts against his Presence/Quality/Responsiveness rubric, and produces structured output across the 7 categories in his Version Map.
4. The two-folder dashboard structure described in the Version Map: 8 conversation-type folders (Discovery, Strategy/Recommendation, Closing, Onboarding/Implementation, Service/Review, Coaching, Other Conversation) sorted chronologically, plus relationship folders (one per target person). Transcripts and scorecards auto-file to the correct conversation-type folder after review.
5. The multi-section scorecard structure described in the Version Map: call metadata, overall score with graph, best moment, top 3 strengths, top 3 missed opportunities, category breakdown across the 7 categories, one coaching focus, suggested phrase for next time, "in this moment, here is what could be said better," recommended next steps (thank-you note, email, document send, calendar event, referral ask), final summary, and an HTML link to the full uploaded text.
6. Pre-upload input fields capturing desired outcome of the conversation or relationship, and relationship type (Inside circle / Referral partner / Existing client / Prospective client).
7. Joint decision documentation on the three open V1 questions: data storage location and security model, usage caps per user per time period, and, if Option B is selected, payment processor and integration approach.
8. Source code in Christian's GitHub with operating instructions for ongoing reference.
9. A payment flow that gates access for new users. Implemented via Kajabi if feasible (Christian's existing platform), or Stripe or another processor as fallback if Kajabi does not support the use case.
10. A 2-week post-launch bug-fix window beginning on the date of the Final Handoff session. Bug fixes only. New features handled as a separate engagement.

Client Time Commitment

Christian's active time commitment is capped at approximately 3 hours total across the 4-week build period. This covers the four scheduled sessions (one 60-minute Kickoff, two 30-minute milestone reviews, one 30-minute milestone review, and one 60-minute Final Handoff). Additional asynchronous review of build progress is optional and typically requires 20 to 30 minutes per milestone.

The engagement is designed so Christian spends his time on decisions and direction, not on execution. Execution work is handled by Natalee.

Roles and Responsibilities

Natalee Champlin leads all engagement work: account setup support, codebase migration to Christian's GitHub, backend build (Supabase, authentication, secured storage), AI scoring integration with Christian's rubric, dashboard and filing structure build, scorecard build, pre-upload input field implementation, optional payment integration (Option B), deployment to Christian's domain, operating documentation, all milestone reviews, and the Final Handoff.

Christian Hansen participates in the four scheduled sessions, provides decisions during the Kickoff Session on the three open V1 questions, provides his Anthropic API key, provides two test transcripts (one deliberately weak, one deliberately strong) for AI scoring validation, sets up the accounts the production app will live on (Vercel, Supabase, GitHub, Anthropic, with Natalee guiding setup during Kickoff), and confirms domain choice no later than the end of Week 1.

Out of Scope

The following are explicitly not included in this engagement:

• Coach Dashboard, Admin Dashboard, and any features described in Version Map V2 (search, analytics, trend graphs, tags, custom folder creation, post-login survey, coaching center). These are scoped as a separate future engagement if Christian wants them.
• Version Map V3 features: book text ingestion with page references, relationship intelligence tool. Separate future engagement if desired.
• Ongoing hosting fees, including Vercel, Supabase, Anthropic API tokens, and domain registration. These accounts belong to Christian and are billed to Christian directly by their providers.
• Marketing, sales support, or onboarding materials for Christian's clients or coaches who use the product.
• Training Christian's coaches or admin staff on how to use or operate the product.
• Ongoing operational support, daily maintenance, feature additions, or design changes beyond the 2-week post-launch bug-fix window. Continuation is a separate engagement if mutually desired.

Change Management

Any change to the scope of this engagement requires written agreement from Natalee Champlin and Christian Hansen. Work beyond the SOW scope is handled as a separate engagement with its own terms. This protects the 4-week timeline and ensures V1 delivers what was promised.

Payment

Total: $7,500.

• 50% ($3,750) due upon signing.
• 50% ($3,750) due Monday, June 8, 2026 (two weeks after engagement start).

Payment covers the full scope above, including the payment integration deliverable. No additional charges for the engagement period or the 2-week post-launch bug-fix window.

Engagement Close and Continuation

The engagement formally closes at the end of the 2-week post-launch bug-fix window, on Friday, July 3, 2026. Any continuation, expansion to V2 or V3, or other new engagement is discussed at Christian's discretion after engagement close and scoped as a separate SOW.

Acknowledgment

By signing below, all parties acknowledge agreement to the scope, deliverables, roles, and terms described above.