Module 7: Building an Implementation Proposal

Duration: ~75 minutes self-paced Prerequisites: Modules 1-6 Learning objectives: - Convert a Maturity Map report into a scoped implementation proposal - Define milestones tied to maturity score improvements - Set success metrics that the client can verify independently - Handle the most common objections without discounting - Sell the per-touch schema-change stewardship product as a standard line item, not a retainer - Include a per-touch price list as a proposal appendix that anchors expectations

7.1 The Proposal Structure

Use the provided template templates/proposal_template.md. Sections in order:

1. Cover — Client name, your name and certification badge, date, validity period (30 days standard)
2. Executive summary — One paragraph. The pain, the path, the price.
3. Current state — Pulled directly from the Maturity Map report. Do not re-litigate the scoring.
4. Proposed scope — Phased intervention sequence with concrete deliverables per phase
5. Milestones and success metrics — Each phase has one measurable improvement
6. Pricing — Phased, with optional add-ons separated
7. Assumptions and exclusions — Clear about what is not in scope
8. Terms — Payment schedule, change order process, IP ownership

Keep the whole thing under 8 pages. SMB owners do not read 30-page proposals.

Vocabulary for client-facing documents

Use the terms your client's leadership is hearing from their industry analysts and conferences:

• "Context graph" instead of "knowledge graph" or "RDF triplestore" - it conveys the same architecture but signals awareness of the current market conversation
• "Decision traces" instead of "audit logs" - it positions the governance layer as strategic infrastructure, not compliance overhead
• "Structural governance" instead of "data governance" - it signals that the governance is built into the data, not managed in a separate tool
• "The missing why" - Foundation Capital's framing for what context graphs provide. Your proposal should show how the SDC engagement delivers exactly this.

The executive summary is where this vocabulary matters most. A CTO who has been reading about "context graphs as AI's trillion dollar opportunity" should recognize their problem in your first paragraph - and see your proposal as the concrete path to the infrastructure their analysts have been describing.

7.2 Scoping from the Map

The Maturity Map gives you the sequence (Module 5). The proposal converts that sequence into phases.

A typical 12-month proposal for a Level 1-2 client looks like:

Each phase 0-5 has a fixed-price quote. Phase 6 is structurally different — see §7.7 below. The client can stop after any of phases 0-5 and still keep Phase 6 indefinitely. They almost never stop, but the option matters.

7.3 Success Metrics That Hold Up

Bad metrics: "improved data quality," "better governance," "faster reporting." These are unmeasurable and unenforceable.

Good metrics: tied directly to the Maturity Map dimension and verifiable from artifacts.

The point is that the client can run the verification themselves after you leave. They are not dependent on you to confirm the work was done.

7.4 Handling Pricing Objections

"Your competitor is half the price." Response: "What is in their scope? If they are also delivering schema enforcement, validators, audit logging, and an annual reassessment, I would like to see how they price that. If their scope is narrower, then we are not comparing the same engagement."

"Can we do it in half the time?" Response: "We can compress phases 1 and 2 into one if you can dedicate a technical lead full-time during those weeks. The total fee is the same; the calendar shrinks. That is the only lever."

"Can you discount if we do all phases?" Response: "I can offer 5% off phases 4-6 if all phases are committed up front, with payment due at the start of each phase. The reason I cannot discount more is that the framework is designed to deliver verified value at each phase, which is what protects you if we discover something unexpected."

"We want to start with governance." Response: "I understand the appeal — governance is what your board asks about. The reason the framework starts with schema is that governance over an unstable schema produces audit findings instead of audit confidence. If you want, I can show you a one-page memo on what happens to governance programs deployed before schema enforcement."

(Have that memo ready. It is in templates/governance_first_warning.md.)

7.5 Phase 6: The Schema-Change Stewardship Product

This is the most economically important section of the proposal and the one most practitioners get wrong on their first few engagements. Read Module 5 §5.7 if you have not already; this section assumes you know what a "touch" is.

Phase 6 is not a retainer

A retainer is a fixed monthly fee in exchange for an undefined amount of work. Practitioners who structure Phase 6 as a retainer either lose money (when the client demands a lot) or train the client to ignore them (when the client demands nothing and feels they are paying for air). Both outcomes are bad.

Phase 6 is a published per-touch price list. The client commits to nothing on a calendar. They call you when their data changes. You touch the system. They are billed for that touch. The next month they may have zero touches or six. Both are fine.

What goes in the proposal

In Section 4 (Total Investment) of the proposal template, Phase 6 appears as a separate line:

Phase 6 — Schema-change stewardship Per-touch pricing per the published rate card (Appendix C). No minimum, no monthly commitment, no cancellation. Typical clients average 4-12 touches per year as their environment evolves.

In Section 5 (Success Metrics), Phase 6 has its own metric:

Phase 6: Same-day redeployment of any agreed-scope schema change with no downtime to the production application.

In Appendix C (new), include the per-touch price list directly. Use the table from Module 5 §5.7 as the starting point and adjust to your market and experience level.

Why same-day matters

The differentiator that closes Phase 6 in the original conversation is same-day. Your client has spent years experiencing data changes as multi-week IT projects. The first time you tell them "you call me at 9am, you have a redeployed application by 4pm, you are billed $1,500" they will not believe you. The first time you actually deliver it, they will tell every peer they know.

Same-day is not a marketing claim. It is what the touch workflow (Module 5 §5.7) actually produces for the lower-complexity touch types. Set expectations accurately: a single-field addition is same-day; a major refactor is multi-day. The price list reflects this.

How to introduce Phase 6 in the proposal walkthrough

When you walk the client through the proposal in person, do not glue Phase 6 to the end of phases 1-5 as an afterthought. Treat it as the answer to a question they have not asked yet: "what happens after the first 6 months?"

Recommended walkthrough language (memorize this):

"Phases 1 through 5 build the foundation. Phase 6 is what makes that foundation worth having for the next ten years. Your data will change — new fields, new sources, new regulations, new business lines, mergers. Every change in a traditional setup is a multi-week project that you postpone until you cannot. In our setup, every change is a same-day touch. You call me, I touch the system, you have a redeployed application that afternoon. You pay per touch, with no monthly commitment. There is no minimum and no cancellation. You only pay when something actually changes. Most of my clients average somewhere between 4 and 12 touches per year. The price list is in Appendix C — take a look and tell me if anything looks wrong. And one more thing: you will never face a forced software upgrade, and you will never have to migrate your data. The application lives on your hardware, in your environment, on your timeline. Indefinitely."

Then stop talking. Watch the client's face when they read the price list. Watch them realize that for the first time in their career someone is offering them continuous evolution of their data infrastructure at predictable, transparent prices with no SaaS vendor in the middle, with no upgrade calendar they cannot control, and with no migration risk.

Why the "no forced upgrades, no migrations" line is the one that closes the deal: Most SMB owners have personally lived through a forced SaaS upgrade that broke a workflow, or a migration that lost historical data they cared about. They remember it. They tell the story at industry events. When you offer them a model where it cannot happen again, you are not making a marketing claim — you are removing a specific scar tissue. The recognition on their face when they understand this is the moment you have closed the engagement.

Phase 6 closes the deal

In practice, Phase 6 frequently closes engagements that phases 1-5 alone would not. A client who is on the fence about $40,000 of foundation work commits when they realize the foundation work also gives them access to the touch product going forward. The foundation is the entry ticket; the stewardship is the recurring product.

This is the part of the practitioner business model that you, the practitioner, are selling. Do not be shy about it.

7.6 Assumptions and Exclusions

The most important section nobody reads until something goes wrong. Be specific.

Standard assumptions: - Client provides read-only credentials for in-scope datasources within 5 business days of contract signing - Client designates one technical lead available for 4 hours per week during active phases - Client provides a Linux host or laptop for SDCforSMB installation - SDCStudio wallet has sufficient balance (estimate provided in pricing section)

Standard exclusions: - Data cleanup of historical records (separate engagement) - Migration of data from existing systems (separate engagement) - Custom UI development beyond the SDCforSMB defaults - Training of end users on the generated applications - 24/7 support or formal SLA (not part of the standard practitioner engagement)

7.7 Terms That Protect Both Sides

• Payment: 50% at phase start, 50% at phase completion. Net 15. No 50% upfront for the whole project.
• Change orders: Anything outside the proposal scope is a written change order. No verbal scope creep.
• IP: All generated code, schemas, and validators belong to the client. Your assessment methodology and templates remain yours.
• Termination: Either party may terminate at the end of any phase with 10 days notice. Completed phases are non-refundable.
• Confidentiality: Mutual NDA, default 3 years.
• Reference rights: You may name the client as a customer in your marketing after Phase 1 completes, unless they opt out in writing.

Module 7 Final Exercise

Using the fictional exercises/case_atlas_legal.md Maturity Map results from prior modules, produce a complete implementation proposal using the template. Cap it at 8 pages. Include:

• Phased scope with milestones
• Success metrics per phase
• Pricing that totals between $25,000 and $60,000 across all phases
• A specific exclusion related to a request the client made during the assessment

Submit via the certification portal. This is the capstone artifact for Tier 2 certification.

After Certification

Once you pass the Tier 2 exam and submit the capstone proposal, you receive:

• The SDC Certified Practitioner badge and directory listing
• Access to the practitioner private community
• The full templates library (proposals, contracts, sales decks, leave-behinds)
• Quarterly framework updates
• Quarterly framework updates and access to refined pricing benchmarks from the practitioner community

Welcome to the program. The framework gets stronger every time a practitioner uses it in the field. Send feedback.