Picture this

Who it is for

Priya registers for a 48 hour event with three sponsor tracks. Hack Week Pilot reads the rules, flags eligibility traps like fresh-code requirements, builds a timeline, and on Sunday morning drafts the README and demo script.

Two ways to own it

What you get

Base$169

$42 deposit to reserve

Rules parser, eligibility checklist, team board, submission and demo-script drafts, onchain team commit timestamp.

You choose: name and logo
You choose: accent color
You choose: default chain

Customfrom $1,200

Built around you

Reshape it entirely: new features, your flows, your brand end to end, integrations you need. We scope it with you.

Everything in Base
Custom features and design
Priority build

Why it is new

What exists today, and what this does differently

Why own your own

Hackathon AI copilots already exist; this would compete on web3 bounty depth.

Closest things out there

HackPilot plans scope, generates Devpost copy and scores submission readiness, and HackaRag maps ideas to bounties.

Checked with web searches in October 2026. A search is not proof that nothing similar exists, and the market moves fast, so we recheck before every build.

What it unlocks

The human in it

Gives first-time hackers the playbook veterans keep in their heads.

The Regatta Board

Races it can enter

hackathon · Encode Club · rolling

Encode Club hackathons and accelerators

rolling calendar; specifics unknown

Official page ↗

Builder tooling for hackers; varies per event.

Their rule on existing code: unknown; varies per event

hackathon · DoraHacks · rolling

DoraHacks BUIDL hackathons and grants

rolling

Official page ↗

Many DoraHacks events accept existing BUIDLs.

Their rule on existing code: Varies; many DoraHacks events accept existing BUIDLs

What you own

The whole app, not a starter kit.

The complete Hack Week Pilot app: a first time hacker gets every rule and linked document read, traps flagged, a plan checked against the clock, a timestamped kickoff commit and Sunday drafts of the README and demo, with a paywall and pilot agent built in.

Base price · $169

The user app, complete

Every buyer gets the same finished app. Basic branding and copy changes come through a quick form.

Three step onboardingHome

Shown once: read every rule, plan against the clock, ship something that works.

Weekend status and next actionHome

Hours, tracks, sprints, recent activity and one next step.

Rules reader and trap checklistRules

Reads the event page and linked PDFs, flags the fresh code and signed APK traps.

Kickoff commit timestampRules

A fresh repo with the first commit timestamped onchain.

Sponsor bounty notesRules

What each sponsor track judges actually check. Gated behind Pilot.

Flight plan and runway checkPlan

Tracks, hours and team size against focused hours, with a cut scope path.

README and demo draftsSubmit

Every claim linked to a commit. Gated behind Pilot.

Submission receiptSubmit

Kickoff and submission hashes; prizes never promised.

Weekly practice sprintsSubmit

A 2 hour sprint each week with a streak. Gated behind Pilot.

Plans and USDC checkoutMe

Cadet, Pilot and Club tiers through the shared USDC checkout.

Open the full app demo

Add-on

Owner console

Your admin side: revenue, paywall editor, users, rules and the agent log.

Revenue and paywall editorRevenue

MRR, incoming USDC, payment methods, tiers and gates.

Pilot rulesRules

Timestamp chain, linked document rechecks and one track default for first timers.

Pilot agent logAgent

The missed PDF rule and the slipped timeline, and how it changed, plus costs.

Roadmap build requestsRoadmap

v2 and v3 scopes with add-on prices.

Top-up

Growth and referrals

Referral and growth mechanics, switched on when you are ready to grow.

Shipped share cardSubmit

Share what the team shipped after submitting.

Event partnership loop and referralsGrowth

Partner with an event, club licences, sprint list and referrals.

The money path, built in

How it earns for you

Rules and traps are free; hackers pay monthly for Pilot and clubs or organizers buy licences, in USDC.

CadetFreeRules reader, trap checklist, runway planner, kickoff timestamp

Pilot$12 a monthSunday README and demo drafts, weekly sprints, sponsor bounty notes

Club$299 a monthEvery member of a university club or event gets Pilot

Timestamps cost a few cents per team per event.

Prices are yours to set. Illustrative, not a promise of income.

Growth loops, built in

How it spreads

Share cards after each event
Club licences bringing whole cohorts
A weekly sprint list between events
Trap of the week posts from parsed rules

Roadmap · build the next phase with us

Where it goes next

v1 included

The full pilot

Rules reader with linked documents
Trap checklist
Runway planner
Kickoff commit timestamp
Sunday drafts and paywall

Included

Organizer licence

Organizer console
Rule change broadcasts
Judge packets
Fresh code checks at scale

Add-on from $600

Hacker passport

Portable hackathon history
Trap of the week posts
Team matching
Sponsor bounty marketplace

Add-on from $1,100

For investors and grant reviewers

The pitch, ready

The veteran's hackathon playbook in a first timer's pocket.

Problem: First time hackers lose to fine print and overscoped plans, not to weak ideas.

Solution: Every rule read and checked, a plan against the clock, a timestamped fresh repo and honest Sunday drafts.

Why now: Web3 and AI hackathons run every week with sponsor tracks full of fine print.

Market: Student and early career hackers, plus the clubs and organizers who host them.

The ask: License to five university clubs and two event organizers this quarter.

Funding is never guaranteed. Check each program's rules.

For hackathons and demo days

Your 2 minute demo

Home: Priya, 03:12 in a Bengaluru gym.
Rules: the fresh code trap; timestamp a fresh repo.
Owner Agent: the missed PDF rule fix.
Plan: three tracks do not fit; cut to one.
Submit: drafts gated behind Pilot; submit and share.
Owner Revenue: change the Pilot price.
Owner Growth: partner with an event.
Owner Roadmap: organizer licence and hacker passport.

Many hackathons require code written at the event. See the Regatta Boardfor each race's rule.

Make it entirely yours

Custom event integrations, organizer dashboards, new chains and branded pilots, scoped on a call from $1,000.

Custom from $1,200

BLUEPRINT

Why it matters and how it really works

The need

First time hackers lose weekends to things veterans avoid: rules buried in linked PDFs, fresh code requirements, chasing too many sponsor tracks, and no demo video ten minutes before judging. The playbook lives in veterans' heads.

What exists and what is new

Hackathon AI copilots already exist. HackPilot plans scope, generates Devpost copy and scores submission readiness, and HackaRag maps ideas to bounties. Research verdict: exists, low novelty. This version would compete on web3 bounty depth: reading every linked rules document and diffing changes, flagging chain specific track requirements, an onchain commit timestamp at kickoff for fresh code rules, and a weekly practice loop between events. It is a focused variant, not a new category.

The data it runs on

Public event pages, track pages and linked documents (PDF FAQs), the team's repo commits, the team's chosen tracks, hours and skills, and public bounty boards for weekly sprints. Drafts and notes stay private to the team.

1.The mission

Give every first time hacker the playbook veterans keep in their heads, so they ship something that works and learn faster.

2.Why people can't resist it

The trap alert A red ticket that says this rule would have disqualified you, found in a PDF you never opened. People share that moment.

The runway A live gauge of build hours left versus scope. Seeing OVER BY 12H at hour 17 makes cutting scope feel obvious, not painful.

Sunday sprints A 45 minute weekly task matched to the next event that fits your stack, with a streak.

3.How it works for real

Sign in: Privy email or GitHub login, optional embedded wallet on Base for timestamps. Team invites by link.

Rules reader: Fetches the event page, track pages and every linked document, extracts rules with a mid tier model (for example Claude Sonnet tier) and rechecks on a schedule, diffing changes.

Planner: Scope estimates per track from rules and past public repos, against team hours with a 55% real build factor. Small model tier for routine nudges.

Repo watcher: GitHub webhooks track progress against the plan and feed the readiness score.

Commit timestamps: Kickoff and final commit hashes written to Base (or Solana or Arbitrum) as a tiny transaction or an EAS attestation, so fresh code is checkable.

Drafts: README, track answers and a 2 minute demo script drafted on Sunday morning, each claim linked to a commit, edited by the team.

Notifications: Telegram or Discord bot for rule changes, runway warnings and Sunday sprints.

4.Cost per use and pricing

Per event per team: reading and rechecking rules is roughly 200k to 400k tokens on a mid tier model, a few dollars at most; planner nudges and drafts on smaller models add well under $1. Two onchain timestamps on Base cost a few cents in gas. A club running 30 teams through an event is roughly $50 to $120 in model costs.

Solo Free for one event

Rules reader, traps and runway for a single hackathon.

Team $9 per event

Team board, repo watcher, Sunday drafts and timestamps.

Club $79 a month

For university clubs and bootcamps: many teams, mentors' view, weekly sprints.

5.Growth loop

Share cards after each event, club licences that bring whole cohorts, and the weekly sprint list that brings people back between events.

6.Risks and guardrails

Wrong rule reading: A missed or misread rule can cost a team. Always link the source line, mark confidence, and tell teams to confirm with organisers.

Rule breaking help: Some events ban AI generated code or copy. Read that rule first and switch drafting off when required.

Overpromising: The app never predicts or promises prizes. It helps teams ship; judges decide.

Privacy: Repos and drafts may be private. Only commit hashes go onchain, and only when the team opts in.

Competition: Existing copilots cover planning and copy. Stay focused on web3 track depth and honest scoping.

7.Build order

Rules reader with linked document fetching and diffing
Trap checklist against the team's plan
Runway planner with track estimates
Kickoff commit timestamp on Base
Sunday README and demo script drafts
Weekly sprint and event list

8.Where this is going

Now
A first timer reads every rule and cuts scope at hour 17 instead of hour 40.
Next
Clubs and bootcamps run whole cohorts through events with mentors watching the runway.
Later
Organisers publish machine readable rules and accept checkable fresh code proofs by default.
World changing
Anyone, anywhere, can enter a hackathon with a veteran's playbook and turn a weekend into a real skill.

Costs and tools are estimates at the time of writing. General information only, not legal or financial advice.

OWNER PLAYBOOK

Own it, then chart your voyage

Nine routes from one vessel. Tap a port to open its chart.

Why own Hack Week Pilot

First time hackers lose weekends to the same traps: scope too big, a sponsor rule missed, a README written at 3am. Hack Week Pilot reads the rules, flags eligibility traps like fresh code requirements, plans the timeline, tracks bounties and drafts the submission and demo script. Owning it makes you the cockpit your community uses every hackathon: your brand, your team board, and revenue from every hacker and every organizer who wants better submissions.

What’s stopping you?

“I can't code. Can I run a hackathon tool?”

Yes. The rules parser, eligibility checklist, team board, submission and demo script drafts and onchain team commit timestamp are built. You set the default chain, name and colors, add your AI key and deploy with the guide.

“Is using AI to draft submissions cheating?”

Check each event's rules. The tool drafts; the team edits and owns every word. Encourage hackers to disclose AI help where events ask, and never fake what was built.

“Will it guarantee wins?”

No. It removes avoidable mistakes and saves hours. Judges still reward the idea and the build. Say this plainly.

“What if the rules parser misses something?”

It can. Show the source rule text beside every flag and tell users to confirm with organizers. Collect misses and fix the parser prompts.

“Who pays?”

Hackers who do many events, university clubs that send teams, and organizers who want fewer broken submissions.