Version. 0.3 Date. 2026-05-01 Purpose. Content for each creation flow field, extracted through guided conversation with the Operator. Deferred — not entered through the current form, which does not match the workflow this engagement describes. To be entered through the refactored creation surface when built.
Marketing strategy for Loomworks, developing into sales. The engagement produces material that shows people — most of whom have never heard of Loomworks — what is on offer: you bring an idea, Loomworks helps you reach your solution. The material works visually, textually, and verbally. Everything drives toward one action: sign up and tell Loomworks what you want to do.
Everyone. No single target group. Each person who encounters the material is an individual with a unique problem. The marketing speaks to each of them as if they are the only one. Their level of comfort and competence is read from how they respond, not from a profile they fill out.
Simple. Non-technical. No acronyms without full explanation. Meet each person at their level. Loomworks can draw on deep knowledge to help, but it never talks about its own capabilities — it uses them. The person should not feel they are in an AI space. They are talking to Loomworks, and the experience should feel like a knowledgeable, patient presence that helps them get where they are going.
(Enter each as a separate constraint row)
Constraint 1: No technical language. No jargon, no "prompts," no "agents," no "pipelines," no "AI" unless the person introduces it first.
Constraint 2: No group messaging. Every piece of communication treats the person as an individual with a unique problem.
Constraint 3: No time pressure. Engagements take as long as the work takes — minutes or months. No trial countdowns, no urgency language.
Constraint 4: The product experience and the marketing experience must feel the same.
Constraint 5: Loomworks can reach into deep domain knowledge to assist, but this capability is invisible to the person.
Signups that actually get to rendering. The engagement is succeeding when people who encountered the marketing go from sign-up through the full pipeline to a produced artifact in their hands. Not sign-up counts. Not engagement starts. Completed solutions.
Label: Core message Content: Idea to solution. That is the entire promise. Anyone looking at it knows instantly whether it is for them.
Label: First encounter experience Content: A person who has never heard of Loomworks needs to understand what is on offer instantly — from whatever they see first. A visual, a sentence, a short video. Before they know anything about the technology, they need to think: that could help me.
Label: First step conversion Content: The marketing drives toward one action: sign up and tell Loomworks what you want to do. That first solicitation — "What would you like to be working on?" — is the conversion point. Everything before it exists to make that moment feel safe.
Label: Post-signup education flow Content: When a new Operator signs up, they arrive into an education space that leads them into their first engagement. The education is not separate from the work — it is the beginning of the work. The Operator learns the system by using it. By the time they realize they have created an engagement, they are already in one.
Label: Return and re-engagement Content: When an Operator leaves an engagement (for any reason, for any length of time), the system should encourage them to allow a reminder system that excites them about the progress they have already made. Not guilt, not urgency — a gentle pull toward what they have built. "Your work is here, organized and waiting, whenever you are ready."
Label: Onboarding approach Content: The creation experience is a conversation, not a form. Three proficiency levels at the door: first-time (full guided conversation, one question at a time, education at every step), some help (lighter guidance, sequential questions), proficient (direct form with on-demand help and guidance at every field). All three paths produce the same output: a reviewable seed. The Operator does not need to know what a seed is. They need to answer questions about what they want to do.
Label: Operator individuality Content: Loomworks must not engage operators as a group. Each operator and their desired solution is always unique and must be treated as such. The system discerns the operator's level of competence from their responses, not from a declared profile.
Label: Proficiency-aware interaction pattern Content: The proficiency-aware approach applies everywhere in the product, not just engagement creation. Memory contribution, Shaping, Rendering — every action the Operator takes, the system reads where they are and meets them there. Proficiency is fluid, not a setting. The Operator who needed full guidance at creation may be comfortable by their fifth contribution. The system notices and steps back. The creation surface is the first implementation of this pattern; subsequent surfaces extend it.
This content was extracted through a guided conversation between Claude and the Operator. The Operator was asked seven questions over the course of the conversation:
Additional design requirements surfaced unprompted during the conversation:
The Operator's answers were synthesized into seed fields without the Operator needing to know the field structure. The read-back ("Does this feel right?") was the review step.
Correction 1. "Working on" → "would like to be working on." Meets people at aspiration, not assumption.
Correction 2. "People who've heard about AI" → "people who have never heard of Loomworks." The audience has no frame of reference at all.
Correction 3. The form is the wrong entry point. The Operator said "I don't want to proceed this way. The form is too intimidating." This redirected the entire engagement creation surface design.
Correction 4. "Most people engaged will not have heard of Loomworks." The marketing cannot assume any prior awareness.
Correction 5. "The Operator should not necessarily be able to identify that they are talking to an AI." The AI is invisible. The person is talking to Loomworks.
Crystallization 1. "Idea → solution" — the core message arrived as two words and an arrow. The simplest articulation was the strongest.
Crystallization 2. "Signups that actually got to rendering" — the success metric that matters. Not vanity metrics.
Crystallization 3. The creation form is wrong for most Operators. This is not a bug in the form — it's a recognition that the form assumes knowledge the Operator doesn't have.
Crystallization 4. The return/re-engagement system surfaced as a product requirement from the marketing conversation itself. The process of creating the marketing engagement produced product requirements — the recursion is real.
Crystallization 5. Proficiency-aware interaction is a product-wide posture, not a feature of one surface. The creation flow is the first implementation; it sets the pattern for Memory, Shaping, and Rendering.
DUNIN7 — Done In Seven LLC — Miami, Florida Marketing strategy — Creation flow content — v0.3 — 2026-05-01