about 4 hours ago
8 weeks | Here's how to actually use them ⏱️
Eight weeks sounds like a lot. It isn't. The builders who submit something they're proud of are the ones who had a plan. Here's a rough framework to get you from idea to submission without the last-minute panic.
🗓️ The Slack Agent Builder Challenge Timeline
🌱 Weeks 1–2: Idea → Foundation (May 20 – June 1)
- Pick your track: New Slack Agent, Agent for Good, or Agent for Organizations
- Identify the real problem you're solving — the narrower and more specific, the better
- Decide which technology you're leading with: Agent Builder, MCP, or RTS API
- Set up your developer sandbox and run slack create agent to scaffold your project
- Open your Devpost submission form — you can start saving answers now
🔨 Weeks 3–5: Build (June 2 – June 22)
-
Core functionality first — get your agent doing the thing before you polish anything
-
Drop into the hackathon Slack channel if you hit a wall — Slack engineers are around
-
Draft your architecture diagram early (it's a required submission item — uploaded via file upload on the submission form)
-
If you're targeting the Organizations track, start your Marketplace submission process now — it takes time
✨ Weeks 6–7: Polish + Record (June 23 – July 6)
-
Refine your UX — judges score design separately, so it matters
-
Write and rehearse your video script before you hit record
-
Record your demo video and upload to YouTube or Vimeo (must be publicly visible)
-
Finalize your text description and make sure it explains the impact clearly
🏁 Final Week: Submit + Double-Check (July 7 – July 13)
-
Submit by July 6 if possible — early submissions may get reviewed by Devpost so you can fix any eligibility issues before the deadline
-
Confirm both slackhack@salesforce.com and testing@devpost.com have Member access (not Guest) to your sandbox
-
Make sure all Project teammates have accepted their Devpost invitations
-
Double-check your video is public and plays without a login/error
-
Deadline: July 13, 2026 at 5:00 PM PT. No late submissions.
💡 A Few Planning Tips That Actually Help
-
Solve a real problem, not a demo problem. Agents that do one specific thing really well beat generic chatbot wrappers every time.
-
Name your project like a human, not an AI. Judges read dozens of submissions. "SlackBot Pro 3000" blends in. Pick something memorable.
-
Use the Resources page. The Agent Builder templates, Block Kit guide, and Bolt SDK docs will save you hours.
-
Don't build alone if you don't have to. Post in the hackathon Slack channel [#slack-agent-builder-challenge] to find teammates (note: up to 4 team members allowed).
Go build something. You've got this. 🙌