Custom-domain content cluster
Long-form Dify guides, internal links, disclosures, analytics, partner handoff, and self-serve affiliate routing live on the CREATE SOMETHING site.
Dify Content Engine
Custom-domain content owns the funnel. Substack carries the dispatch.
The Dify affiliate lane needs one canonical place for proof, disclosures, analytics, and lead routing. The CREATE SOMETHING site owns that source of truth; Substack sends readers back to it with a weekly, lightweight cadence.
This is the owned visual for the Dify content engine: one custom-domain article produces dispatches, social clips, ledger evidence, and the lead split.
Created by CREATE SOMETHING for this article.Channel Split
Each surface has one job.
Substack dispatches
Weekly notes summarize one idea, point back to the canonical page, collect replies, and build the subscriber list.
Social and video clips
Native snippets and demos create reach, but the measurable conversion path still resolves to the canonical page.
Collected from Dify's official documentation on 2026-05-25. This is evidence for the article's claim that Dify content should explain workflow packaging, not only chatbot prompts.
Source: Dify Workflow and Chatflow docsTargets
Measure the channel by canonical content, subscribers, and paid conversions.
100-200 subscribers
1-2 paid conversions
300-500 subscribers
4-6 paid conversions
750-1,500 subscribers
20 paid conversions
2,000-3,500 subscribers
50 paid conversions
Content Cluster
Publish the canonical page first, then dispatch the angle.
The long-form asset lives on the custom domain. Substack gets the shortest useful version: one claim, one artifact, one link back.
Builders
Dify + MCP Control Plane
Dify is the surface. MCP is the boundary.
Operators
Dify Agent Eval Gates
The evals that make Dify safer to operate.
Agencies
How To Ship A Dify App With MCP Tools
A practical shipping checklist for Dify plus MCP.
Client buyers
Client-Safe Dify Delivery Evidence
What proof can be public without leaking traces.
Marketplace builders
Dify Template Marketplace Workflow
Turn a Dify workflow into a reusable asset.
Operators
Dify vs n8n: Workflow Automation vs Agent Apps
The job changed: n8n for workflows, Dify for agent apps.
Consultants
Dify Affiliate Starter Kit For Agencies
How agencies should route self-serve Dify leads.
Affiliate Economics
The first serious milestone is 20 paid conversions.
Working model: Dify Professional at $59/month, Team at $159/month, 30% starting commission, 50% after 20 paid conversions, and a 12-month eligible commission window.
Upgrade milestone
70% Professional and 30% Team at the starting 30% rate.
First scaled target
First 20 at 30%, next 30 at 50%, same plan mix.
Mature run rate
First 20 at 30%, next 80 at 50%, same plan mix.
Weekly Loop
Keep the system operational, not theoretical.
Every piece should leave a ledger row, a measured source, and a clear route for self-serve users versus implementation buyers.
- Publish or update the custom-domain page first.
- Add internal links from the Dify and partner pages.
- Keep Dify links direct until affiliate acceptance exists.
- Send a short Substack dispatch back to the canonical page.
- Log the URL, audience, disclosure, link type, and campaign in the ledger.
- Record visits, clicks, affiliate clicks, conversions, and service leads in Linear.
Next Step
Route Dify readers by readiness, not only by booking intent.
Use the checklist for cold readers, the teardown for operators with a live workflow, and the mapping session for buyers ready to scope implementation.
Trust checklist
A low-friction resource for readers who need language for allowed, ask, blocked, logging, and recovery states.
Get Trust ChecklistTrust map
A short form that captures the stack, bottleneck, risk boundary, and first workflow worth mapping.
Request Trust MapMapping session
A calendar path for buyers who already know the workflow, owner, approval authority, and decision timeline.
Map Your Workflow