FlyRank AI Fluency · Intern Guide
Week 10 · Capstone & graduation

Send the Link: Launch, Demo & Story

Ten weeks ago you did not have proof. Today you have a portfolio that is clear, that does a real thing, that holds up when you push on it, and that is filled with your real work. The capstone is the synthesis of all of it, not extra work: the launched site, the demo, and the honest story.

Phase: Submit Estimated hours: 5 Capstone
The idea this week
  • If you build something real and stay quiet about it, it might as well not exist. The story is what turns a nice page into proof that you can take an idea and ship it.
  • The demo is the real thing running, not slides. Show the live site, the working feature, and one place AI did the heavy lifting.
  • When someone asks "can you actually do this?", you will not argue. You will send a link. That is what you did not have when you started: proof, not a claim.

Why it matters

Everything in this track builds toward one thing: proof that you can take an idea and ship something real with AI, and tell the honest story of how. When the capstone is done, you will not have to claim you are good with AI. You will send them a link.

Brief

The capstone has four components, all built across the previous weeks:

  1. The launched portfolio: on your custom domain, proving its one claim, filled with real work, navigable by a stranger in five minutes.
  2. The proof: a public build-in-public story with one real win and one real limitation.
  3. The package: a 3 to 5 minute demo (walk the live portfolio, show the one real feature working, show one place AI did the heavy lifting), plus a short build write-up (the stack you chose and why, the hardest thing that broke, what you would build next), plus your plan to keep building.
  4. The FlyRank loop: the graduate badge installed in your footer linking to your verification page, and the site submitted to the FlyRank showcase. Opt in to a featured case study if you are happy to.
Gated by the two checkpoints: the design review (Week 7) and the hardening review (Week 9). The capstone is what the completion certificate names.

Deliverable

The live custom-domain URL, the 3 to 5 minute demo, the build write-up, and the build-in-public story, posted in your track thread and submitted to the showcase.

Evaluation criteria (pass/revise)

  • The portfolio is live on a real domain and does its one job: a stranger can tell what you do and believe it in five minutes.
  • The one real feature genuinely works in the demo on a fresh try.
  • The demo clearly shows one place AI did the heavy lifting.
  • The write-up names a real stack decision, a real break, and a real next step, specific to this build.
  • The build-in-public story is honest: one real win and one real limitation.
  • A concrete plan to keep building exists (a named next piece plus a real reminder).
  • The badge is installed and the site is submitted to the showcase.
The move this week

Tell the honest story

Not a brag, not a press release. What you made, one thing AI did that you could not have done alone, and one thing that broke and what you learned. Honesty is what makes it read as real.

Prompt · Write the honest launch story
Help me write a short, honest "how I built my portfolio with AI" post, not a brag. Interview me first: what did I make and why, what is the one thing AI did that I could not have done alone, and what is the one thing that broke and what I learned. Ask me one question at a time. Then draft the post in my voice {paste_your_voice_card}, 200 to 300 words, honest about where AI helped. Start.
A worked example

Iris tells the story, and plans her next case

AI assistant
Iris: The domain points to my site and HTTPS is on. Analytics is running.
AI: Plant the flag done. Now the story. What is the one thing I did that you could not have alone?
Iris: You wrote the code so I could spend my time on the design and the decisions. And the contact form broke on empty submissions until we caught it.
AI: That is your post: one honest win, one honest limitation. It reads as someone real, which is what gets hired.
Iris: What do I add next?
AI: The onboarding flow you are redoing at your day job. Same three beats. Put a reminder for the day it ships.

Iris did not just finish a project. She launched a platform she owns and already knows how to keep growing. That is the difference between a class artifact and a career asset.

Dorian wrote his honest post the same day: AI helped him turn a month of messy Instagram notes into a clean before-and-after case, and the share preview broke once before he fixed the title. His next case is already named, the email campaign he is about to run. Same flag, his story.

For your track. The launch is the same for everyone; the demo leans on your proof. Walk the case craft, run the model live, show the metric, or use the tool.
Words you'll hear this week
  • Build-in-public. Telling the honest story of what you made and learned, flaws included.
  • Capstone. Your portfolio itself, launched, plus a short demo and an honest write-up. Your proof.
  • Showcase. The FlyRank page that features your live portfolio and links out to it.
Every term is in the Glossary.
You did it

Ten weeks ago, what you could do with AI was your n: undefined, full of potential. You just solved for it.

You did not study your way into the AI world. You built your way in. You have a real thing you own, on your own domain, filled with your real work, and the habit to keep it growing. When someone asks if you can do this, you will not argue. You will send a link. Now go send it to someone who did not think you could.

One last thing. Your n keeps counting. Every project you ship from here is the next case, indexed into the platform you own. This was week ten. It is also day one of the rest of it.

Linked resources