1 / 30
Fractal-Apps · Workshop · 60 min
CREATE YOUR
OWN AI
PROJECT
Using the SPARK Engine Methodology — Build anything with a team in 30 days.
Website App Content Automation Personal Growth
Nicolas Martin · Fractal-Apps Pvt Ltd
The world changed. Has your workflow?
Problem 01 / 07
The crisis
Most people learn but never build.
Lectures, courses, certifications — all passive. Real value comes from creating something that didn't exist before.
5%
Retained from a lecture after 24 hours
— National Training Laboratories
75%
Retained when you do the work yourself
— Learning Pyramid Research
And AI makes the gap even wider — if you use it wrong.
Problem landscape
Seven reasons entrepreneurs stay stuck
The same 7 blockers.
Over and over.
01
Passivity
Waiting to be taught instead of building
02
No Ownership
Participating without a stake in the outcome
03
Broken Teams
Groups ≠ teams. No roles = chaos
04
AI as a Crutch
Prompt → paste → submit. Zero learning.
05
Purpose Deficit
No why = no energy = no follow-through
06
Cost Barrier
Great programmes are unaffordable
07
ROI Vacuum
No proof you actually changed
Recognise yourself?
These aren't personal failures — they're design failures.
What if there was an operational solution grounded in science?
Problem 04 — AI
The AI trap
Use AI wrong.
Grow weaker.
Automation bias: the tendency to defer to AI even when your own judgment would be more accurate. Repeated enough, it causes cognitive atrophy.
Low-Agency AI Use
Open AI → Type vague request → Accept first output → Submit
Result
Fast, forgettable work. No skill growth. Clients leave.
High-Agency AI Use
Think first → Write prompt → Iterate → Own the output
Result
10× speed. Full understanding. Compounding skill.
The difference is a method. That method is SPARK.
The solution
SPARK
The Engine Methodology
A science-backed, team-based operating system for building real AI projects — in 30 days, with structure, accountability, and proof of growth.
S
Structure
P
Prompt
A
Act
R
Review
K
Keep Going
Let's see what's under the hood — starting with the science.
Science foundation
Why SPARK works — Learning retention
Build a pyramid.
Climb it.
Lecture
5%
Reading
10%
Video
20%
Discussion
50%
Practice
75%
Teaching
90%
SPARK combines discussion, practice, and teaching — in a single sprint. Students in active learning conditions are 1.5× less likely to fail (Freeman et al., 2014).
Motivation matters as much as method. Here's what fuels it.
Science foundation
Self-Determination Theory — Deci & Ryan
3 needs that
drive everything.
Autonomy
Your actions feel like YOUR choice — not an obligation
→ SPARK: You choose your role & project
Competence
You feel yourself growing with each sprint
→ SPARK: Milestones prove progress weekly
Relatedness
Your team is counting on you. That matters.
→ SPARK: TRIO roles + PACE accountability
Traditional education fails all three. SPARK is designed around all three.
Now let's meet the team architecture that makes this real.
Team architecture — The TRIO System
3 roles. 1 team.
Zero wasted effort.
🎯
Captain
The Anchor
  • Runs weekly check-ins
  • Delivers PACE evaluations
  • Mediates conflict
  • Holds the team together
⚙️
Builder
The Engine
  • Executes tasks with AI prompts
  • Produces every deliverable
  • Documents the prompt library
  • Makes the project real
🔭
Scout
The Radar
  • Researches & benchmarks
  • Proposes new ideas each session
  • Tests alternative approaches
  • Protects the team from groupthink
Teams with poorly defined roles spend up to 40% of time in invisible negotiation about who does what. — Belbin, 30 years of data.
Roles are chosen through a wizard — then locked into a contract.
Role assignment — The SPARK Wizard
Find your natural position.
  • 1
    Energy Orientation
    Where does your energy go — managing people, producing output, or exploring ideas?
  • 2
    Working Style
    Structured or exploratory? Individual or collaborative?
  • 3
    Stress Response
    How do you behave under pressure? That's when roles reveal themselves.
Your Role Card includes:
  • Your role + % fit score
  • Your role's superpower
  • Your risk zone + mitigation
  • Your AI partnership style
  • Your first 24-hour action
fractal-apps.com/classes/008-spark-lab-students
Before the team can build, the team must ignite — that's Day 1.
Day 1 — 9 hours
The ignition session
9 hours changes everything.
You cannot build team trust in 2 hours. The sequence matters — nothing is filler.
09:00
Ignite
Icebreaker + AI intro
11:00
Assign
Roles + Team Contract
11:30
Map It
Project scoping + SMART-P
13:30
Build
First AI work sprint
17:00
Show
Cross-team demos
17:45
Wrap
Rituals + group photo
Teams that meet in person on Day 1 maintain higher trust, lower conflict, and higher productivity for the entire project. — Social Physics, MIT Media Lab.
Day 1 plants the seed. Sprints make it grow.
The sprint system — 4 weeks
4 sprints.
1 real product.
Sprint 1
Build Foundations
First real deliverables. Establish rhythms. Normalise difficulty.
Sprint 2
First Contact with Reality
External testing. Pivot if needed. Storming phase peaks here.
Sprint 3
Trainer Visit + Deep Review
Course-correct. Trainer consultation. Quality rises noticeably.
Sprint 4
Final Polish + Demo Day Prep
Complete the project. Prepare 10-min team presentation.
30
Days to a real project
2× sessions/week · 3h each · Team lunches · Demo Day
~50 hours total facilitation
A project with 4 sprint milestones is experienced as 4 achievable wins — not 1 giant obligation. Implementation intentions increase follow-through by 3×. — Gollwitzer (1999).
Every sprint runs the same core loop — the SPARK cycle.
The core loop — runs at every scale
The cycle that
never stops.
S
Structure
Define the problem. Set success criteria. Time-box.
›
P
Prompt
Write PEX prompt in notebook FIRST. Then execute.
›
A
Act
Individual deep work. Produce something real. No interruptions.
›
R
Review
Team reconvenes. 3-min each. Keep, revise, discard.
›
K
Keep Going
Commit to the next cycle. Momentum is the metric.
This loop works at 30 minutes, 3 hours, or 1 week. The fractal that scales.
The 'P' in SPARK is where AI becomes a superpower — not a shortcut.
AI methodology — The PEX Formula
Prompt with
precision.
P
Purpose
What do you REALLY need — not the surface request, but the underlying goal?
❌ "Write a market analysis"
✅ "I need to understand 3 risks for my tiffin delivery startup in Pondicherry"
E
Example
Give AI a reference frame: tone, style, format, length, comparable output.
Friendly. Short sentences. Under 15 words per bullet. Structured as a table with 4 columns.
X
Expected Output
Specify exactly what you want: format, length, structure, perspective.
"A 300-word paragraph for an investor pitch" vs "10 competitive advantages as a list"
The Notebook First Rule: write your PEX prompt in your physical notebook before you type it. This activates slow, deliberate thinking — the kind that produces results AI can't fake.
Great prompts come from great thinking. Let's talk about how you think.
Mindset
High Agency — the hidden variable
Stop waiting.
Start building.
Low Agency
  • "I would have done more, but..."
  • "I'm waiting until I have..."
  • "Someone should really do something about..."
  • Uses AI to skip thinking
  • Blames circumstances for results
High Agency
  • "What am I going to do about this?"
  • Builds before conditions are perfect
  • Takes full ownership of outcomes
  • Uses AI to amplify thinking
  • Owns failures as fast feedback
Agency is not a personality trait. It is a practice. 4 sprints of real stakes and real peers watching changes the way a person shows up — in a project, in a career, in a life.
High agency means communicating as clearly as you think. Enter: CLEAR.
Communication protocol — CLEAR
Teams fail from
silence. Not conflict.
C
Concise
3 elements max: accomplished, blocked, what's next
L
Listen
To understand — not to prepare your counter-argument
E
Engage
Silence is not neutrality. It creates information vacuums.
A
Acknowledge
The first need when someone shares a difficulty: be heard.
R
Record
Every decision in Google Drive. Commitments that are documented are harder to abandon.
The most common cause of team failure is information withheld until it becomes a crisis. CLEAR is a structural intervention against that pattern. — Lencioni, The Five Dysfunctions of a Team.
Communication builds trust. But how do you know it's working? PACE.
Accountability — The PACE Scorecard
Make progress
visible. Weekly.
P
Progress
Task completion vs sprint plan
A
Attitude
Honest + constructive orientation
C
Contribution
Did your work move the project?
E
Engagement
Active presence in team life
Engagement drops before Progress does — it's the early warning signal every Captain watches.
How Captains deliver PACE
  • 1
    Open with one specific positive
  • 2
    Share scores dimension by dimension
  • 3
    For ≤3: ask "What got in the way?"
  • 4
    Agree one change for next sprint
  • 5
    Close with a statement of confidence
PACE creates accountability. Projects create proof. Let's talk about what you'll build.
Your project — what gets built
Real projects.
Not hypotheticals.
Website / Landing Page
A live product for real users — portfolio, business, community.
Example: EcoTiffin brand + landing page
App / Automation
A chatbot, workflow tool, or AI-powered service.
Example: AI job-matching platform
Content System
A newsletter, podcast, digital magazine with AI-assisted production.
Example: Bilingual digital magazine
Personal Improvement Tool
A tracker, habit system, or AI coaching flow for yourself.
Example: 30-day skill builder
Audio / Video Product
AI-guided audio tour, podcast, or explainer series.
Example: Heritage Walk AI — French Quarter tour
Business Model / Strategy
A validated business plan, pricing model, or go-to-market document.
Example: Startup financial model
Projects are structured in 3 layers — so they scale and survive team friction.
Project architecture — 3 layers
Structure that
survives reality.
L1
Master Project
The overarching vision. Large enough to inspire. Specific enough to scope.
L2
Team Tracks
Parallel sub-projects. Teams progress independently — but create more together.
L3
Individual Tasks
Specific, bounded, attributable deliverables. The unit of PACE evaluation.
SMART-P Task Definition
  • Specific — unambiguous description
  • Measurable — done or not done
  • Actionable — skills + tools ready now
  • Realistic — sized for the sprint
  • Time-bound — specific deadline
  • Prompted — AI prompt documented in Drive
Structure creates resilience. But presence creates trust. Why in-person matters.
Neuroscience — why meeting in person is non-negotiable
Screens build walls.
Rooms build trust.
Oxytocin Release
Eye contact and physical proximity trigger the bonding hormone. Trust built in person is deeper and more resilient than trust built through screens.
Neural Synchronisation
Princeton fMRI research shows brain activity literally synchronises during face-to-face conversation. This is the mechanism of genuine understanding — not just information exchange.
The Lunch Effect
MIT Social Physics: teams that ate lunch together consistently outperformed those that didn't. SPARK includes team lunches as a formal, structured programme component.
Teams that had at least ONE in-person meeting at project start maintained higher trust, lower conflict, and higher productivity through the entire remote phase. — Distributed Teams Research.
Trust built in person pays dividends across every digital interaction that follows.
~2 min
The finish line — Demo Day
Demo Day is a
graduation + a launch.
  • 1
    Present 10 minutes
    Problem, approach, tools, obstacles, what's next
  • 2
    Answer 5 minutes Q&A
    From peers, facilitator, and any external guests
  • 3
    Receive your Certificate
    Named role, named project — a credential with content
  • 4
    Access the alumni network
    Drive stays open. Community stays active. Projects continue.
Your certificate marks:
  • Day 1 (9 hours in-person)
  • 4 completed sprints
  • A real deliverable built
  • A public presentation delivered
Not attendance. Completion.
The project ends. The network begins. That's the real long-term value.
~2 min
Long-term value — the network effect
Your real output:
a professional network that knows your work.
"The professional opportunities that most change people's trajectories come through acquaintances — people they know well enough to trust, but not so well that their networks entirely overlap."
— Granovetter (1973), The Strength of Weak Ties
A SPARK cohort of 40 people spans tech, media, startups, language, culture — all of these domains simultaneously accessible through your alumni network.
Post-programme patterns
  • Teams continue their projects after Demo Day
  • Alumni introduce SPARK peers at new employers
  • Significant repeat participation in later cohorts
  • Cross-cohort network grows denser with every programme
The community WhatsApp stays open. Always.
Let's make the ROI concrete. What does this actually return?
~2 min
Investment return
The ROI — specific and measurable
₹7,000 in.
Career capital out.
Immediate Outputs
  • Portfolio project (real, shareable)
  • Documented AI prompting skills
  • Role credential (Captain / Builder / Scout)
  • Full PACE growth record
Network Capital
  • Multi-domain peer community
  • Peers who know your work ethic directly
  • Facilitator as credible connector
  • Alumni referrals + collaboration
Skill Development
  • Collaboration under real pressure
  • AI tool mastery (PEX method)
  • Project management experience
  • Public presentation delivered
Break-even: a single professional introduction from the alumni network that leads to a project, job, or collaboration. In practice — this occurs with high frequency.
Entrepreneurs benefit in a uniquely powerful way — here's how.
~2 min
SPARK for entrepreneurs — specifically
Stop building
alone.
The Solo Founder Problem
Isolation is one of the most underreported causes of startup failure — not just emotional, but cognitive. Thinking without an interlocutor produces blind spots. Planning without accountability produces inertia.
What SPARK gives entrepreneurs
  • The structure of a co-founding team — without the complexity
  • Complementary perspectives that expose blind spots
  • Honest feedback that clients won't give you
  • The social contract that keeps everyone moving
What you'll have after 30 days
1
Real product built
3
Trusted teammates
4
Sprint cycles completed
∞
Network that stays
The science behind all of this is well-established. Let's recap it quickly.
~2 min
Why it works — science recap
Built on 70 years
of research.
MOTIVATION
Self-Determination Theory
Autonomy + Competence + Relatedness = intrinsic drive. Deci & Ryan.
COMMITMENT
Lewin's Field Theory
Public commitments produce 3–10× higher follow-through. Team Contract = Lewin intervention.
TEAM THINKING
Asch's Conformity
One dissenter protects the team from groupthink. The Scout role is a structural Asch intervention.
SKILL GROWTH
Vygotsky's ZPD
Learning happens at the upper edge of ability — with appropriate support. Sprint escalation is ZPD design.
BELIEF
Bandura's Self-Efficacy
Believing you can changes what you can. Milestones + PACE + Demo Day are efficacy engineering.
ENGAGEMENT
Csikszentmihalyi's Flow
Challenge matched to skill + clear goals + real stakes = deep encoding. SPARK creates these conditions.
Theory is proof. But what does the experience actually look like day-to-day?
~2 min
Experience — a typical sprint session
3 hours.
Real output created.
  • 00:00
    WATCH Check-In
    Captain shares blockers. Team energy scan. One highlight from last session.
  • 00:20
    Notebook + Prompt Design
    Each member writes their PEX prompt in their notebook. No AI yet.
  • 00:35
    Deep Work Sprint
    Individual AI-assisted execution. Protected focus time. Builder produces. Scout researches.
  • 02:00
    Team Review (3 min/person)
    Show output. Captain leads debrief. Keep, revise, discard decisions.
  • 02:45
    Keep Going — Next Sprint Commit
    WhatsApp update. Drive logged. Next session tasks assigned.
What you walk out with
  • A real deliverable (not a plan — an output)
  • Prompts documented in the shared library
  • Clear next action for each team member
  • A Captain's Drive log entry
"A rough prototype that exists is worth more than a perfect specification that doesn't."
Now you've seen SPARK from every angle. What does it take to get started?
~2 min
Getting started — minimum requirements
Less than you
think you need.
Space
A café, coworking space, or community hall. Tables that move. Whiteboard optional. Good light essential.
Materials
1 physical notebook per person (essential). A pen. A laptop or phone with internet. Access to Claude or ChatGPT (free tier works).
Time
Day 1: 9 hours. 8 sessions of 3h over 4 weeks. 4 team lunches. 1 Demo Day (~4h). Total: ~50 hours.
₹7,000
Full month programme · India
$160
USA & Europe
Student & group discounts available
Group of 3–4: ₹500 off/person · Students: ₹6,500 flat
You've seen the framework. Now let's talk about your project specifically.
~2 min
Your roadmap — 30 days to a real project
Mark your
calendar today.
Day 1
Ignite
9h in-person · Roles + Contract + First Sprint
W1
Sprint 1
Build foundations · First deliverable exists
W2
Sprint 2
External test · Pivot if needed
W3
Sprint 3
Trainer visit · Deep review · Quality rises
W4
Sprint 4
Final polish · Demo prep
D30
Demo Day 🎓
Present · Certificate · Network
30 days is not long. But 30 days structured as 4 sprints — with a team, a role, real stakes, and a Demo Day — is transformative. The same duration. A completely different experience.
Three things to remember before the final slide.
~1 min
The 3 things to remember
Build. Together. Now.
1
Struggle is a feature
The hard part IS the learning. Don't reduce difficulty — stay in it for one full cycle first.
2
Real output over perfect plans
A rough first draft that exists is worth more than a perfect specification that doesn't.
3
Prompt from your notebook
Write before you type. Think before you prompt. Own the output — not just the paste.
One slide left. One decision to make.
The question you came here with
Do you have an
idea worth building?
Most entrepreneurs have 3–7 ideas they've been meaning to start. The gap between having an idea and having a product is not more thinking — it's structure, accountability, and teammates.
5
Cohorts per year
25
Max participants
30
Days to your project
⚡ Next cohort filling now
Limited to 25 seats to preserve the quality of the team experience. Once full — next cohort only.
Here's exactly what to do next.
Your call to action
Use AI. Build
with a team.
In 30 days.
FINISH YOUR PROJECT
IN 30 DAYS.
Join the next SPARK Engine cohort →
sparkengine@fractal-apps.com
fractal-apps.com
Nicolas Martin Fractal-Apps Pvt Ltd Pondicherry · France
Role Wizard: fractal-apps.com/classes/008-spark-lab-students