TaskSprint: The Weekend-Only Gig Platform

TaskSprint was born from a simple observation: most gig platforms are always-on, which creates friction for one-off, time-sensitive tasks. We wanted to build something that felt like a neighborhood bulletin board, but digital and only alive on weekends. The vision: a minimalist web app where you can post a task (e.g., 'assemble IKEA furniture Saturday afternoon') and a local doer can claim it. The entire experience is compressed into the weekend—tasks must be scheduled for Saturday or Sunday, and the platform goes dark Sunday at 11 PM. This creates urgency and a community vibe. The MVP was built by a team of three (developer, designer, marketer) over a single weekend, using Firebase for real-time data, React for the frontend, and cash/Venmo for payments. We launched with a handful of friends and local Facebook groups, managing the first transactions manually via WhatsApp. The prototype is still live at a private URL, but we never scaled it beyond that initial test.

Existing gig platforms like TaskRabbit and Fiverr are always available, which can overwhelm users with choices and make one-off tasks feel too formal. People often need something done this weekend and want a quick, local connection without the overhead of profile building, escrow, and high fees. Also, these platforms take 15-20% cuts, which discourages both posters and doers for small tasks.

• Launch a working MVP on Sunday night after 72 hours of coding
• Onboard 50 users (task posters and doers) within first month via local Facebook groups
• Facilitate 10 completed tasks within first two weekends
• Keep platform fees at 5% (much lower than competitors)
• Build a trust system using mutual ratings and WhatsApp verification

• Not building a mobile app (web-only MVP)
• Not supporting recurring tasks (only one-time weekend tasks)
• Not offering dispute resolution (rely on cash/reputation)
• Not expanding beyond one zip code initially
• Not building an escrow system (pay after completion)

• Frontend: React (create-react-app) with Tailwind CSS for quick styling
• Backend: Firebase Firestore (serverless, real-time) + Firebase Auth
• Payments: Cash on completion (no integration needed)
• Communication: WhatsApp (manual grouping, no API)
• Deployment: Vercel for frontend, Firebase hosting for backend
• Collaboration: Figma for design mockups, Notion for planning, Discord for team chat

Single-page web app with a marketplace view. Users sign up with phone number (verified via Firebase). Task posters create a task with description, date (Saturday or Sunday), location, and price they are willing to pay. Doers browse tasks sorted by distance and date. They accept a task and the poster gets a notification via email (free tier SendGrid). After the task, both parties rate each other on a 1-5 scale. The platform stores all data in Firestore with 'tasks' and 'users' collections. No real-time payments; cash or Venmo handled off-platform. The site goes live Friday 5 PM and goes into 'offline' mode Sunday 11 PM (a cron job deactivates buttons).

• Trust and safety: since no payment processing, risk of no-shows or disputes
• Low volume: critical mass needed for both sides
• Weekend-only availability might frustrate users who want midweek service
• Manual WhatsApp group management isn't scalable
• Legal liability for tasks (e.g., injury during work)

• How to verify users without SSN? Use phone number and check spam calls?
• Should we implement a simple badge system for top doers?
• What's the best way to handle cancellations? Penalty for no-shows?
• Should we allow tasks that require special skills (e.g., plumbing)?
• How to prevent spammy task posts?

The team had a great weekend building the prototype, but then real life kicked in — jobs, other projects, and the complexity of scaling a trust-based marketplace without legal backing felt daunting. The prototype sits on a private GitHub repo, and occasionally someone asks about it, but it never got past that weekend.

We used the 'ludicrous mode' approach: everything manual except the listing itself. The WhatsApp group had 12 people by Sunday night. It was exhausting but fun.