Create Your Own AI Project — SPARK Practical Toolkit

SPARK Engine · Practical Workshop

CREATE
YOUR
OWN
AI
PROJECT

A hands-on toolkit: role-adapted prompts, smart tools, strategic tips — everything you need to go from idea to launch in 30 days.

Your roles today

🎯

Captain

Structure · Accountability · People

⚙️

Builder

Execute · Prompt · Produce

🔭

Scout

Research · Benchmark · Challenge

The promise

Finish your project
in 30 days.

Nicolas Martin · Fractal-Apps Pvt Ltd

Structure · Prompt · Act · Review · Keep Going

Before we start

How to read this deck

Role-Tagged Content

Every prompt, tip, and tool is labelled by role: 🎯 Captain · ⚙️ Builder · 🔭 Scout. Find yours — and study the others.

Tip Boxes

Coloured boxes = actionable advice from SPARK practitioners. Teal = strategy. Amber = tool recommendation. Coral = warning. Violet = soft skill.

PEX Prompts

Dark blocks = ready-to-use AI prompts in PEX format (Purpose · Example · Expected Output). Copy to notebook. Refine. Execute.

Tool Chips

Each tool section lists the best AI tools for that task — colour-coded by category. "There Is An AI For That" is your starting search.

The golden rule: Write every prompt in your physical notebook before typing it into any AI tool. This activates deliberate thinking — the kind that produces outputs worth using.

Notebook first. Always.

Sprint 0 — Before you build

Strategic foundation

Search for the best strategy
before writing a single line.

Most projects fail not from lack of effort — but from building in the wrong direction. Spend Sprint 0 answering 3 strategic questions.

01

Does it already exist?

Search for existing tools, products, competitors. If it exists, is yours 10× better or 10× cheaper?

🔭 Scout task

02

Who is it really for?

Define 1 specific user. Not "entrepreneurs" — "a 28-year-old freelance designer in Pondicherry with 3 clients and no CRM."

⚙️ Builder task

03

What's the minimum first version?

The smallest thing that could be real and useful to one person. Not an MVP — a VSP: Viable Single Product.

🎯 Captain task

Start here: Go to theresanaiforthat.com and search your project idea. If 3+ tools already exist, you need a sharper angle — not a different idea.

Strategy before execution. Always.

Tool landscape — the AI universe

There Is An AI
For That.

theresanaiforthat.com — 5,000+ AI tools indexed by use case. Your Scout's first stop every sprint.

Writing & Content

Claude ChatGPT Jasper

Design & Visuals

Canva AI Midjourney Adobe Firefly

Slides & Decks

Gamma Beautiful.ai Tome

Audio & Voice

ElevenLabs Descript Murf

Research & Synthesis

Perplexity NotebookLM Elicit

Build Own Tools

Tool Generator ↗ Claude API

Scout tip: Don't test tools at random. Benchmark 3 tools on the same task using identical PEX prompts. Document which produced the best output and why. Share results in the WhatsApp group.

Use the best tool for the job — not the most famous one.

Fractal-Apps · Tool Generator

Build custom AI tools

No tool exists for
your exact need?
Build one.

The Fractal-Apps Tool Generator creates custom AI-powered tools from a description — no code required. Your Builder generates the tool. Your Scout tests it. Your Captain documents it.

fractal-apps.com/en/services/tool-generator

What you can generate

Custom prompt generators for your project type
Presentation builders with your brand voice
Research tools tailored to your industry
Training & quiz generators for soft skills

Sprint workflow

1

Sprint 1

Describe your tool's purpose in 2 sentences. Use the Generator. Get a first version.

2

Sprint 2

Test on 3 real use cases. Collect friction points. Refine the description. Regenerate.

3

Sprint 3–4

Deploy tool to the team. Include it in the Demo Day presentation as a live product.

A custom tool built during your SPARK sprint becomes a portfolio artefact — not just a project deliverable.

The best projects build tools — not just documents.

AI methodology — core skill

The PEX Formula:
Purpose · Example · Expected Output

P

Purpose

What do you REALLY need? Not the surface request — the underlying goal. Write the actual problem you're solving.

❌ "Write a bio"
✅ "I'm pitching to a French investor next week. I need a 60-word founder bio that highlights my AI + local market expertise."

E

Example

Give AI a reference frame: tone, style, format, length. The more specific, the better. Your domain knowledge improves this.

"Confident, first-person, present tense. Short sentences. Avoid corporate jargon. Similar tone to Paul Graham's essays."

X

Expected Output

Specify exactly what you want. Format, length, structure, perspective. Forces you to think about how you'll use the output.

"3 versions, 60 words each. Label each by tone: Direct / Warm / Bold."

Notebook First Rule: Write your full PEX prompt in your physical notebook before touching your keyboard. This one habit separates skilled AI users from prompt-and-paste users.

Never accept the first AI output. Iterate at least once.

🎯 Captain — Role Prompts

Role-adapted prompts · Captain

🎯 Captain — Use AI to
lead and structure.

[PURPOSE] I'm the Captain of a SPARK team. We're in Sprint 1. I need to create a clear project scope and 4-sprint milestone plan for building [your project].

[EXAMPLE] Output should look like a project brief a product manager would share with a startup team. Bullet-point milestones, one per sprint.

[EXPECTED] A sprint plan table: Sprint | Goal | Key Deliverable | Success Criterion. 4 rows. Realistic for 6h/week of team work.

[PURPOSE] I need to write a PACE feedback message for a Builder who missed their Sprint 2 deliverable. I want to be direct but supportive — not punitive.

[EXAMPLE] Tone: a coach speaking to a teammate they believe in. Not a manager writing a warning. Under 120 words.

[EXPECTED] A short spoken-word script I can use in our 1-on-1. End with one concrete action for Sprint 3.

Captain AI workflow

Use AI to generate the Team Contract template on Day 1
Use AI to create the weekly Check-In agenda (5 min)
Use AI to draft WhatsApp update templates for each sprint
Use AI to generate conflict-resolution talking points
Use AI to write the final PACE report narrative

Captain rule: You are not the best prompter on your team — but you ARE responsible for making sure everyone's prompts are documented in the shared Drive.

Soft skill to exercise

Active listening in check-ins

Ask AI: "Give me 5 open questions a team leader can ask at the start of a weekly sprint check-in to surface hidden blockers."

The Captain leads by asking — not by telling.

⚙️ Builder — Role Prompts

Role-adapted prompts · Builder

⚙️ Builder — Use AI to
execute fast and well.

[PURPOSE] I'm building [specific deliverable, e.g. a landing page for an eco-tiffin startup]. I need the hero section copy: headline, sub-headline, and one CTA button label.

[EXAMPLE] Tone: warm, direct, sustainability-forward. Think Oatly meets Zomato. No buzzwords. Under 20 words for the headline.

[EXPECTED] 3 options for each element. Present as a table: Option | Headline | Sub-headline | CTA. I'll pick one and iterate.

[PURPOSE] I need to build a research summary document for our Scout's findings from Sprint 2. Make it readable for a non-technical team member.

[EXAMPLE] Format: each section max 3 bullet points. Plain language. Use analogies if a concept is abstract.

[EXPECTED] A Google Doc-ready Markdown template: Title, 3 sections (Market, Competitors, Risks), each with 3 bullets and 1 key insight.

Builder AI workflow

Use AI to convert rough notes into a structured first draft
Use AI to generate variations of any copy (3 options minimum)
Use AI to create image/graphic briefs for Canva AI or Midjourney
Use AI to proofread and improve tone in one pass
Use AI to format outputs into the team's Google Drive template

Builder warning: Never submit the first AI output. Read it critically. Change at least one thing. Make it yours — the team needs your judgment, not the AI's first draft.

Soft skill to exercise

Receiving feedback without defensiveness

Ask AI: "Teach me a 3-step technique for receiving critical feedback on my work without becoming defensive."

Production speed matters. Quality matters more. AI helps with both.

🔭 Scout — Role Prompts

Role-adapted prompts · Scout

🔭 Scout — Use AI to
see further ahead.

[PURPOSE] I'm scouting the competitive landscape for [project type] in [geographic market]. I need to find the top 5 existing solutions and understand what they do best and worst.

[EXAMPLE] Output like a startup benchmarking report. Honest, specific. Don't just list features — identify the strategic gap that our project could fill.

[EXPECTED] A comparison table: Tool Name | Strengths | Weaknesses | Price | Strategic Gap. Then 1 paragraph: "Our opportunity is..."

[PURPOSE] I want to propose a major pivot to our team's direction after Sprint 2 user testing. I need to make a compelling case without creating conflict.

[EXAMPLE] Frame it like a scientist presenting new data — not as criticism of past decisions. Calm, evidence-based, forward-looking.

[EXPECTED] A 90-second spoken argument structure: 1. What the data showed. 2. What this changes. 3. What I propose. 4. What I'm asking for from the team.

Scout AI workflow

Use Perplexity for current web research (not ChatGPT — it hallucinates dates)
Use Claude for synthesising long competitor documents
Use AI to generate 3 alternative project directions at any sprint
Use AI to simulate user feedback before actual testing
Use NotebookLM to analyse research PDFs in seconds

Scout rule: Your job is to make the team smarter — not to be the smartest person in the room. Share everything you find, including things that challenge the current direction.

Soft skill to exercise

Presenting challenging ideas without conflict

Ask AI: "How do I propose a major change to my team's direction in a way that invites discussion rather than defensiveness?"

The best Scout is the one who says what others didn't think to look for.

Sprint 0 — Research

Research tools — before you build

Research like a
professional analyst.

Market Research

Perplexity — real-time web synthesis
Statista — market size data
Google Trends — demand signals
Claude — analyse market reports

User Research

Tally.so — fast AI-assisted surveys
Claude — simulate user personas
Reddit — raw user pain points
Product Hunt — competitor reviews

Competitor Intelligence

SimilarWeb — traffic analysis
LinkedIn — team + funding signals
Claude — SWOT from a URL
There Is An AI — tool landscape

[PURPOSE] 🔭 Scout Sprint 0 research prompt: I need a rapid market intelligence brief for [project idea] in [market/city]. This will guide our Sprint 1 direction.

[EXAMPLE] Think like a VC analyst doing a 2-hour diligence. Honest, data-backed, no marketing fluff. Include what's missing from the market.

[EXPECTED] 5 sections: Market Size · Top 3 Competitors · User Pain Points · Our Opportunity · 3 Questions We Must Validate in Sprint 1.

Research before building saves more time than it costs.

Soft skills — learn & practise with AI

Use AI to grow
as a human,
not just as a builder.

The most underused application of AI in team projects: learning the soft skills that will determine whether the team succeeds or implodes.

🎯 For Captains

Ask AI to teach you active listening techniques
Ask AI to simulate a difficult team conversation
Ask AI for a weekly motivation speech for your specific team situation

⚙️ For Builders

Ask AI to teach you how to present your work in 3 minutes
Ask AI for feedback on a draft as a critical reader
Ask AI to help you say "no" to scope creep diplomatically

🔭 For Scouts

Ask AI to teach you how to present challenging data calmly
Ask AI to help you write a pivot proposal that doesn't trigger defensiveness
Ask AI to debrief on a difficult team dynamic you experienced

🤝 For the whole team

Use AI to generate a team retrospective quiz after each sprint
Use AI to create a soft-skills scenario game to play at lunch
Use AI to design a 10-min "conflict-to-clarity" workshop

Soft skills are the bottleneck most AI tools ignore.

Sprint 1 — Week 1

Sprint 1 · Build foundations

Produce something
real by Friday.

🎯 Captain — Sprint 1 checklist

Set up shared Google Drive folder with 4 sprint subfolders
Create Team Contract using AI template (see Slide 7)
Assign SMART-P tasks to Builder and Scout
Post first WhatsApp team update by end of Day 1
Complete first PACE evaluation by Friday

⚙️ Builder — Sprint 1 deliverable

Produce one tangible output — a draft, a prototype section, a content piece, a data table. Something that EXISTS.
Document minimum 3 PEX prompts used in the Drive Prompt Library

🔭 Scout — Sprint 1 deliverable

Competitive research summary (5 competitors, 1 page)
3 alternative approaches for the team to consider in the Sprint Review
Tool recommendation: the 1 AI tool we should add to our stack this sprint

[PURPOSE] End of Sprint 1 team review. I need to summarise what we built, what worked, and what to change in Sprint 2.

[EXAMPLE] Like a startup weekly standup written by a thoughtful PM. Honest about gaps. 1 page max.

[EXPECTED] 4 sections: Built This Week | What Worked | What Didn't | Sprint 2 Priority (1 item only).

A rough first draft that exists beats a perfect plan that doesn't.

Project type — Website

If your project is a website

Build a live site
in Sprint 1–2.

Design (no code)

Framer — AI website builder, publish in 1 day
Webflow — professional CMS
Carrd — 1-page site in 30 min

Copy & Content

Claude — hero copy + SEO pages
Jasper — brand voice consistency
Canva AI — graphics + social assets

Custom AI Features

Tool Generator — embed custom AI tool on site
Voiceflow — AI chatbot for your site
Botpress — no-code AI agent

[PURPOSE] ⚙️ I'm building the homepage for [project]. I need a complete copywriting brief: headline, 3 value propositions, social proof section, and CTA.

[EXAMPLE] Reference: Stripe's homepage clarity meets Notion's human warmth. Under 200 words total on the page. Every sentence earns its place.

[EXPECTED] A structured brief I can paste into Framer/Webflow. Sections labelled. Placeholder text marked with [brackets].

Sprint 1 goal for website teams: Have a published URL by end of Sprint 1 — even if it's just a single-page Carrd. "Published" beats "being designed" every time.

Ship an ugly live site before a beautiful mockup.

Project type — App / Automation

If your project is an app or automation

Automate one
real workflow
per sprint.

No-Code Apps

Glide
Bubble
Adalo

Automation

Make.com
Zapier
n8n

AI Agents

Tool Generator
Voiceflow
Stack AI

[PURPOSE] ⚙️ I need to build an automation that [describe workflow, e.g. collects form responses and sends a personalised email]. I'm using Make.com. I'm a beginner.

[EXAMPLE] Explain like a 10-step recipe. Name each Make.com module I need. Include where I'll hit friction.

[EXPECTED] Step-by-step build guide with module names + settings + 1 common mistake per step to avoid.

Sprint strategy for app teams

1
Sprint 1: Working prototype with hardcoded data. Prove the concept moves.
2
Sprint 2: Connect real data sources. First live test with 1 real user.
3
Sprint 3: Add the AI feature. Document the prompt that powers it.
4
Sprint 4: Polish UX. Document for handover. Demo Day demo prep.

Scout tip for app teams: In Sprint 1, use the Tool Generator to build a simple custom AI tool. This gets your team comfortable with AI integration before the complexity of Sprint 3.

One working automation per sprint. Not ten planned ones.

Project type — Content

If your project is a content system

Build a content machine,
not just content.

Claude — long-form writing Descript — podcast/video editing ElevenLabs — AI voiceover Canva AI — visual content Beehiiv — newsletter platform Notion AI — content planning Tool Generator — content brief tool

[PURPOSE] ⚙️ I need to build a repeatable content production system for [newsletter/podcast/Instagram] about [topic]. The team must be able to run it without me every week.

[EXAMPLE] Think like an editorial director creating a production manual for a small team. Each step should take under 20 minutes.

[EXPECTED] A production checklist: Day | Task | Tool | Time Required | Output. 5 rows max per piece of content.

The content sprint structure

1

Sprint 1: Content Pillars + Pilot Issue

Define 3 content pillars. Produce 1 complete piece using AI. Publish it somewhere real.

2

Sprint 2: Audience feedback + format refinement

Share with 10 real readers. What did they skip? What did they screenshot? Adapt.

3

Sprint 3–4: Systematise and automate

Build the production checklist. Create prompt templates for each content type. Make it repeatable without you.

Key metric: Can a new team member produce a piece using your system — without asking you for help? If not, it's not a system yet.

Content without a system is just work. Content with a system is a product.

Sprint 2 — Week 2

Sprint 2 · First contact with reality

Test your work.
Be surprised.
Adapt.

Sprint 2 must-do: external testing

Share your Sprint 1 output with 1 real potential user — not a friend who'll be polite
Ask: "What confused you?" not "What did you think?"
Scout benchmarks your work against 2 competitors
Captain leads a structured 20-min team debrief on findings

[PURPOSE] 🎯 We just received user feedback on our Sprint 1 output. Some of it conflicts with our original direction. I need to help the team process it without panic.

[EXAMPLE] Frame like a product manager running a post-testing debrief. Separate signal from noise. Keep the team focused.

[EXPECTED] A 20-min debrief agenda: What we heard | What it means | What we change | What we keep. Include 3 grounding questions to open with.

Should you pivot?

✅ Pivot when:

Users don't understand the core value. The problem you're solving isn't the one they actually have. A competitor is already doing it significantly better.

⛔ Don't pivot when:

You received negative feedback from 1 person. The feedback is about aesthetics, not fundamentals. You're just uncomfortable with the direction.

Scout rule for Sprint 2: Propose at minimum 1 alternative approach based on your research. Even if the team doesn't adopt it — the act of considering it strengthens the final direction.

External feedback is the most valuable data your team will collect.

Project type — Personal improvement

If your project is about personal growth

Build the tool
you wish existed.

Personal improvement tools are the most underbuilt category in AI. You understand the user perfectly — because you are the user.

📓

Habit & progress tracker

Daily AI check-in bot — you report, it reflects back patterns you don't see

🧠

AI learning coach

A custom Claude prompt that teaches you a skill at exactly your level, daily

🎯

Goal accountability system

Weekly review prompt + progress visualisation built with the Tool Generator

💪

Skill challenge generator

A tool that creates a new micro-challenge each day in your target skill area

[PURPOSE] ⚙️ I want to build a personal improvement tool for [skill/habit]. I need to design its core interaction loop — what the user does, what AI does, and what changes over time.

[EXAMPLE] Think like a product designer creating a habit app. The loop should take under 5 minutes per day and produce a visible output each session.

[EXPECTED] A "Core Loop Design" doc: User Input → AI Processing → Output + Reflection → What changes over 30 days. One diagram, one paragraph per step.

Sprint tip: Use the Fractal-Apps Tool Generator to build your improvement tool in Sprint 1. Use yourself as the first user for Sprints 1–2. Share with 3 others in Sprint 3.

Team exercise idea

Sprint retrospective with AI

At the end of each sprint: each team member asks Claude "Based on what I've described, what's the one thing I'm avoiding that would most improve my contribution?" Share answers openly.

The best personal tool is the one you actually use every day.

Sprint 3 — Week 3

Sprint 3 · Trainer visit + deep review

This sprint:
quality visibly rises.

Before the trainer visit — prepare:

1
Captain prepares a 3-minute status presentation covering: what we built, where we are, our #1 blocker
2
Builder prepares to show the Prompt Library — at least 8 documented prompts by Sprint 3
3
Scout prepares 3 alternative next steps the team hasn't considered — ready to propose in the visit

[PURPOSE] 🎯 I need to present my team's Sprint 3 progress to a trainer/mentor in 3 minutes. I want to show honest progress, acknowledge what's not working, and get specific advice.

[EXAMPLE] Like a startup founder pitching to an advisor — direct, no spin, show the gap between where we are and where we need to be.

[EXPECTED] A 3-min spoken script: Context (30s) | What we built (60s) | Our blocker (30s) | The question we need answered (30s).

Sprint 3 AI quality upgrade

Prompt Library audit

In Sprint 3, the Scout reviews every prompt in the library and proposes improved versions using PEX. The team votes on the top 3 improvements.

[PURPOSE] 🔭 Review this prompt from our Sprint 1 library: [paste prompt]. Rewrite it using the PEX formula so it produces a 30% better output.

[EXPECTED] Original prompt | Why it's weak | Improved PEX version | What changes in the output.

Sprint 3 milestone: By end of this week, a stranger should be able to understand what you built and why. If they can't — your Demo Day prep starts here.

Sprint 3 is when teams either accelerate or stall. Acceleration is a choice.

AI for continuous learning — all roles

Use AI to learn
what your project demands.

Learn any skill on demand

Khanmigo — AI tutor (maths, science)
Claude — "teach me X as if I'm a total beginner with 1 week to learn it"
NotebookLM — turn any PDF into a podcast lecture

"Teach me [skill] in 5 sessions of 15 minutes each. Start with session 1. Give me a practice task at the end."

Build expertise fast

Perplexity — "explain the current state of [field] in 2025"
Elicit — academic paper synthesis
Claude — "what are the 5 things experts know about X that beginners don't?"

"Act as a senior [role] and quiz me on [topic]. Give me feedback on each answer."

Practice with AI roleplay

Claude — simulate a client meeting, investor pitch, or difficult conversation
ChatGPT — act as a sceptical user testing your product
Claude — debrief a real conversation you just had

"Roleplay as a sceptical investor. I'll pitch my project. Give me harsh but fair feedback."

Team learning ritual: At the start of each sprint session, one team member shares "one thing I learned from AI this week that changed how I'm thinking about our project." 3 minutes max. Document in the Drive.

Every sprint is a learning opportunity — if you design it that way.

Core practice — Prompt Library

The prompt library — your team's intellectual asset

Document every
prompt you use.
Build a library.

The shared Prompt Library in Google Drive is the most valuable artefact your team will produce. Not the project — the prompts that built it.

Folder structure

📁 Sprint 1 Prompts/
  📄 Research_Prompts.md
  📄 Writing_Prompts.md
  📄 Design_Briefs.md
📁 Sprint 2 Prompts/
  📄 User_Testing_Prompts.md
  📄 Pivot_Analysis.md
📁 Best_Prompts_Library.md ← shared across sprints

Each prompt entry includes

Task description · Tool used · Full PEX prompt · Quality rating (1–5) · What you'd change next time

Prompt quality metrics

⭐⭐⭐⭐⭐

First output needed no editing. Could be reused for similar tasks.

⭐⭐⭐

Output needed one round of editing. Prompt can be improved.

⭐

Output missed the mark. Rewrite the Purpose section and retry.

Demo Day asset: Present your Best Prompts Library as a live deliverable. Employers and collaborators value documented AI methodology as much as the project itself.

The prompt library is proof you thought, not just pasted.

Team exercises — present & practise together

AI-generated
team rituals.

Use AI to design team exercises that build the soft skills your project demands — and present them in your sprint sessions.

🎯 5-min check-in ritual

One sentence per person: "Right now I am [feeling] because [reason]. This sprint I need [one thing]."

AI prompt: "Generate 5 variants of this ritual for a tech team in sprint week 2."

🔎 Assumption surfacer

Each member writes 2 assumptions they're making about the project. Share. Identify which ones have never been tested.

AI prompt: "Generate 10 common hidden assumptions for a team building [project type]."

⚡ Pre-mortem exercise

It's Sprint 4. The project failed. Write the 3 reasons why in 2 minutes. Share. Fix the top issue now.

AI prompt: "Facilitate a pre-mortem for a [project type] team in Sprint 2. Generate the top 5 failure scenarios."

🏆 Public win board

End each session: each person names one thing a teammate did this week that helped the project. Specific. Not "great work."

AI prompt: "Generate 5 prompts to help team members give specific, meaningful peer praise."

The team that reflects together outperforms the team that just executes.

Soft skill — Conflict & Communication

When things get hard

Use AI as a
communication coach.

🎯 Captain: when the team is stuck

[PURPOSE] My team hasn't made progress this sprint. One member is disengaged. There's unspoken tension. I need to address this without making it worse.

[EXAMPLE] Give me a framework a therapist + project manager would use. Not corporate HR language.

[EXPECTED] A 3-step action sequence for the next 48 hours. Private first, then team. Include exact opening lines.

⚙️ Builder: saying no to scope creep

[PURPOSE] My Captain keeps adding tasks to my sprint without removing others. I need to push back clearly without damaging our relationship.

[EXAMPLE] Direct but warm. Collaborative framing. Not defensive.

[EXPECTED] 2-3 sentence script I can use in our next check-in. Then a boundary-setting template for future sprints.

🔭 Scout: proposing a direction change

[PURPOSE] I've found research that suggests our Sprint 2 direction is wrong. The team is emotionally invested. I need to present this without triggering defensiveness.

[EXAMPLE] Scientific evidence framing. "The data is saying something we didn't expect" — not "you were wrong."

[EXPECTED] A 90-second spoken proposal structure + 3 questions to open discussion rather than close it.

Team exercise: CLEAR practice

The 3-minute honest update

Once per sprint, each member gives a 3-minute update using only CLEAR: Concise · Listen (others) · Engage · Acknowledge · Record. No preparation allowed. Pure honesty.

Ask AI: "Facilitate a CLEAR communication exercise for our sprint review. Generate 3 honest self-assessment prompts."

Hard conversations done well are worth more than weeks of smooth silence.

Sprint 4 — Week 4

Sprint 4 · Final polish + Demo Day prep

Finish it.
Then present it.

Track 1: Complete the project

The core deliverable exists in full — not "almost done"
Tested or reviewed by at least 1 external person
Documented in Google Drive (anyone can understand it without you)
Prompt Library is clean, rated, and archived

Track 2: Build the Demo Day story

[PURPOSE] 🎯 I need to structure our 10-minute Demo Day presentation for [project]. We want to tell a compelling story, not just show features.

[EXAMPLE] Like a TED talk format + product demo. Emotion first, evidence second, call-to-action third. Each member presents their own contribution.

Demo Day AI toolkit

Gamma

Generate the Demo Day slide deck from your Drive notes in 5 minutes

Claude

Practice Q&A — ask Claude to roleplay as a sceptical audience member

ElevenLabs

Create an AI voiceover for any video or audio product demo

Tool Generator

Show a live custom AI tool as part of your Demo Day demonstration

Rehearsal tip: Present to Claude first. Say: "I'm about to present my SPARK project. Ask me the 5 hardest questions the audience might ask." Prepare for all 5.

Demo Day is not the end. It's the first public moment of something real.

Tool strategy — Claude vs ChatGPT vs Perplexity

Choose the right
AI for the job.

🤖

Claude

Best for

Long-form writing with consistent voice
Nuanced analysis of complex documents
Structured outputs (tables, frameworks)
Sensitive communication drafting
Building custom tools via API

💬

ChatGPT

Best for

Brainstorming and ideation at speed
Conversation-style iteration
Coding assistance (GPT-4o)
Image generation (DALL·E)
Voice mode for speaking practice

🔍

Perplexity

Best for

Current real-world data (2024–2025)
Market research with source links
Competitor intelligence
When hallucination would be dangerous
Quick fact-checking of AI outputs

Best practice: Use Perplexity to research → Claude to synthesise and write → ChatGPT to iterate and brainstorm alternatives. Three tools, each in its zone of excellence.

Use the right AI like a master chef uses the right knife.

Accountability — PACE

PACE evaluation — in practice

Accountability
makes you
better. Use it.

P

Progress

Did you complete what you committed to? Score 1–5. If 3 or below: what blocked you? This is data, not judgment.

A

Attitude

Are you honest and constructive — even when things are hard? A 5 is NOT "always positive." A 5 is truthful and team-first.

C

Contribution

Did your work move the project? High progress + low contribution = producing without impact. Both matter.

E

Engagement

Active presence in team life. The early warning signal — watch for it dropping before Progress does.

[PURPOSE] 🎯 I need to write this week's PACE feedback for [team member]. Their scores: P=4, A=3, C=3, E=2. I want to address the engagement drop directly but supportively.

[EXAMPLE] A coach speaking to someone they believe in, not a manager delivering a warning. Specific. Forward-looking.

[EXPECTED] A 90-second spoken script for our 1-on-1. End with: 1 specific change for next sprint + a statement of confidence.

Self-PACE for all roles

Score yourself before the Captain does

Each Friday: rate your own P, A, C, E. Compare to the Captain's scores. The gap between self-perception and team perception is where the growth happens.

Ask AI: "Help me reflect honestly on my contribution this week using the PACE framework. I'll describe what I did and you ask me hard questions."

The team that measures itself honestly improves faster than the one that doesn't.

Demo Day

Demo Day — present like a pro

Your 10 minutes.
Make them count.

Presentation structure (10 min)