Bespoke Build Intake

This form gathers everything needed to build a custom version of the Kindling Commons framework for your practice. You already know how the app works — use it as a reference as you complete each section. The questions map directly to its architecture.

Take your time. Notes fields are included throughout — use them freely. If you're not sure about something, say so; a question mark is more useful than a guess. When you're done, click Download Responses at the bottom to save a JSON file and send it to David.

Nothing is submitted online. All data stays in your browser until you download it.

01 Identity & Brand Name, colour, voice
In the Kindling Commons this is the header bar, the logo, the colour palette, and the overall feel. Think about how your brand should land for your clients when they first see the tool.
02 Vocabulary Renaming the core concepts
The Kindling Commons uses Strand, Loom, and Weave as its core metaphor. Your tool needs its own language. Below are the concepts — give each one the name that fits your practice. Leave blank if the default works fine.
03 Coaching Frameworks The equivalent of Looms
In the Kindling Commons, Looms are the journey arcs — WTR Spiral, Rite of Passage, Theory U etc. Each has phases. Your tool needs at least one framework with named phases. Add as many as you offer.
For each framework: give it a name, a short description, and list its phases in order. For each phase, give its name and a one-line aim. The more specific you are here, the better the build.
04 Practice Types / Categories The equivalent of WTR, SONG, CfL etc.
Each strand type in the Kindling Commons has a circular icon, a colour, and a short description that appears in the type info pill. In your tool, these are the categories of practice. What are they? Add as many as you need.
05 Practice Database The equivalent of the Strand Bank
The Strand Bank is powered by Airtable. Each strand has: Name, Type, Description, Facilitator notes, Duration min/max, Phase tag, Skill level, Care level, Reflection questions, Contributor/attribution. Your practice database needs the same structure — you populate it in Airtable.
06 Session Structure The equivalent of the Day Planner
In the Kindling Commons, the Day Planner schedules practices into days with clock times, meals and breaks. In your tool, this becomes the session planner. Think through how your sessions are structured and what the planner needs to show.
07 Client & Programme Information The equivalent of Intentions & Group Info
In the Kindling Commons, the Intentions dropdown captures: Who is this for? What do they need? What do we hope for? Any other notes. In your tool, this is the client intake / programme setup. What questions do you need answered before designing a programme?
08 Recurring Practices The equivalent of Rhythms & Rituals
Rhythms & Rituals in the Kindling Commons are practices that run through every day — a morning meditation, a daily check-in. In your tool, these would be practices that appear in every session, or recurring homework. Do you have these?
09 Quick Resource Deck The equivalent of Sparks
Sparks in the Kindling Commons are 43 energisers and icebreakers — a quick-reach resource separate from the main practice bank. In your tool, this might be check-in questions, quick exercises, journalling prompts, or in-the-moment interventions.
10 Care, Ethics & Safeguarding The equivalent of the Care Hub
The Kindling Commons has a Care Hub — somatic practices, trauma-informed guidance, and traffic-light skill/care indicators on every card. Your tool may need something similar, or something quite different, depending on your client population.
11 Export & Output The equivalent of the Facilitator Guide
The Kindling Commons exports a formatted HTML facilitator guide — loom summary, intentions, phases with practice notes, day plan. In your tool, this becomes the coaching plan or session guide. Think carefully about what it needs to contain and who reads it.
12 Team & Access Who uses the tool
13 Anything Else Things that don't fit above

Ready to download?

Click below to download your responses as a JSON file. Send that file to David — along with any existing content, spreadsheets, or documents — and we'll get started on the build scoping.

Nothing has been sent anywhere. This file only exists on your device until you share it.