Baseline and scope
Confirm the SDK, version, use case, sandbox, rights review, and the tracker baseline.
FDI method
Growth Cartography is the method behind Marketing Engineering: evidence first, one supervised loop, measurable handoff.
Marketing Engineering · Developer adoption
From awareness to a working SDK.
A 30-day sprint for B2B SDK and platform teams. Design a clearer path from first discovery to a working first integration with a tested repository, useful technical content, and bounded engineering support.
The path
Four places a developer gets unstuck.
Each lane exists to shorten the distance between reading about your SDK and seeing it run.
- 01GitHub
Give developers a useful starting point.
One runnable starter repo and two technical docs written so a person or an AI assistant can find, read, and run them.
- 02Discord and communities
Help them get it working.
Up to two 60-minute debugging sessions that your team owns and runs, with a creator when one participates.
- 03Reddit and Stack Overflow
Share what is working.
Prepare self-contained technical answers and build notes. Participate only with genuine relevance, permission, and the venue’s disclosure rules.
- 04LinkedIn
Amplify the people doing the work.
Creator-authorized ad preparation for your paid media owner. We prepare it. You launch it, if you choose to.
Deliverables
What you get in 30 days.
- 1
SDK, version, and use case
One of each, chosen in the audit so the whole sprint points at a single first integration.
- 1
Runnable starter repo
Clone, follow the sandbox setup, run. Tested before handoff; no credentials in the example code.
- 2
Technical docs
A quickstart and a task guide, structured for search and AI retrieval.
- 6
Reusable content drafts
Posts and answers for your team or creators to edit and publish.
- 2
Creators, shortlist and brief
Up to two candidates with a brief. Not guaranteed to accept.
- 2
Debugging sessions
Up to two 60-minute sessions, client-owned, with prepared questions.
- 1
Baseline and activation tracker
Editable CSV/JSONL and a local report tool, or your existing approved sheet. Sandbox and live signals stay separate.
- 4
Weekly reviews and handoff
A short review each week, then a final handoff of every file.
Readiness-led channel preparation and permitted participation are included. If creator or community permission is unavailable, we use engineer-led demos and owned docs instead. Campaign launch and media spend are not included.
Content and permissions
Review the technical docs, prepare six drafts and the creator shortlist, check channel permissions.
Support and measurement
Run the first client-owned session if ready, prepare LinkedIn materials, reconcile activation evidence.
Evidence and handoff
Run the second session if ready, refine the repo and docs, hand off with costs and a final report.
Evaluate it
The terms, plainly.
You provide
- An SDK sandbox that works for outside developers.
- One engineer, about 12 hours a month plus session attendance.
- A rights and security review of the public repo and docs.
- A commercial owner, about 4 hours in total.
- Approvals within 2 business days.
We provide
- A solo FDI owner, capped at 80 hours, about 20 hours a week.
- Weekly reviews and a documented final handoff.
- A readiness verdict before the sprint starts.
No 24/7 technical support. If readiness fails, we delay the start or reduce scope.
Not promised
- Creator participation or any specific creator.
- Reach, activation, pipeline, or revenue.
- Appearing in AI answers or AI search results.
- Launching or managing a paid campaign.
Tools and measurement
Measure from the first week, with honest limits.
We work with the tools you already run: your repo host, community platforms, CRM, and product analytics. We do not require a particular vendor and we do not resell one.
- Tracked Repo clones and stars, docs visits, sandbox key creation, first successful call, as far as your systems record them.
- Self-reported A discovery question asking developers how they found you.
- Separated Anonymous attention is never merged with named records. A click is not an integration.
- Human decision Qualified pipeline is marked by a person on your team, never inferred.
- Not claimed Full multi-touch attribution. Without a consented cross-session identifier it is not defensible.
Step one
Tell us about the SDK.
The first step is a short conversation about readiness and a Signal Audit, our separate $2,000 diagnostic. The sprint is only proposed after that.
Request a conversation
Prefer email? john@ratcliffe-lee.com
Get the editable owner kit
A complete editable operating kit: readiness and proposal templates, daily delivery calendar, channel playbooks, runnable local SDK example, CSV/JSONL measurement tracker, and a repeatable sandbox dry run. Downloads as a zip after accepted email capture.
Questions
Before you ask.
Is $10,000 a quote or a price list?
It is a suggested fixed price for a 30-day sprint, confirmed in writing only after the readiness check and a Signal Audit. There is no checkout on this page. Third-party spend such as ads, creator fees, bounties, tools, and hosting is excluded.
Do I have to buy the Signal Audit first?
A Signal Audit is the entry point: a separate $2,000 diagnostic. It tests whether your SDK, sandbox, and team are ready. If readiness fails, we delay the sprint or reduce its scope instead of selling you a plan that cannot ship.
Is the audit fee credited toward the Sprint?
For new proposals, if you start the Developer Adoption Sprint within 30 calendar days of the audit readout, the full $2,000 audit fee is credited toward the Sprint fee. Eligibility depends on the Sprint start date, not the signature date alone. At the suggested $10,000 Sprint fee, that leaves $8,000 for the Sprint after credit, plus the separately paid $2,000 Audit: $10,000 total before excluded costs. Existing signed agreements remain unchanged.
What does my engineer actually do?
About 12 hours a month plus attendance at up to two 60-minute debugging sessions you own. They review the starter repo and docs for technical accuracy, keep the sandbox working, and answer the questions only your team can.
Will you guarantee creators, reach, activation, pipeline, or AI visibility?
No. We prepare a shortlist and brief for up to two creators. They decide whether to participate and what to say. Reach, activation, pipeline, and appearing in AI answers depend on factors neither of us controls, so none are promised.
Do you launch the LinkedIn campaign?
No. We prepare creator-authorized LinkedIn ad materials and hand them to your paid media owner. Launching, budget, and spend stay with you.
Who is doing the work?
A solo FDI owner, capped at 80 hours across the sprint, roughly 20 hours a week. There is no 24/7 technical support. Debugging sessions are scheduled, and your team owns the product answers.
What do you need from us?
An SDK sandbox, one engineer, a rights and security review for the public repo and docs, a commercial owner (about 4 hours total), and approvals within 2 business days. Slow approvals move the dates.
How is success measured?
A baseline and activation tracker records first-integration events you already collect, plus self-reported discovery from developers. Anonymous attention is kept separate from attributable records. A click is never counted as an integration, and a form entry is never a qualified lead until a human says so.
Is the inquiry form a newsletter signup?
No. It is a contact request. We use it to reply about this offer. The owner kit is a separate form with its own consent and a marketing subscription that needs email confirmation.
Part of Marketing Engineering, built on the Growth Cartography method.