1. Write the case study
60 minWrite one page about Hack Week Pilot: the problem, what you set up and decided, what happened, and what you would change. What it caught, what you shipped. Decisions and lessons matter more to readers than polish.
Pick where you want to go. Every route starts with a move you can make within the hour.
Write one page about Hack Week Pilot: the problem, what you set up and decided, what happened, and what you would change. What it caught, what you shipped. Decisions and lessons matter more to readers than polish.
Add concrete figures from Hack Week Pilot such as teams using the cockpit, with dates, to the page. Small honest numbers beat vague claims.
Post a cockpit plan and submission with a two line story on LinkedIn and X, and pin it. Use a headline that names the skill, not the tool.
I built a hackathon cockpit and used it to ship [project] in 48 hours: [link]
Send a cockpit plan and submission with a short, specific note to five teams or people you would like to work with. Mention one thing about their work so it is clearly not a mass message.
Here's tooling I built and two projects I shipped with it: [link].
Leave an email and we nudge you at 24 and 72 hours with your next move. Optional.
Or to keep this voyage on your profile.
A public, verifiable work history for any AI agent, built from the jobs it actually finished.
Your onchain resume: every credential, deploy, and attestation on one domain you own.
Every commit, deploy, and demo you ship becomes a signed, timestamped builder diary.