Government Contract Finder for Small Businesses

AI Prompts to Build This

Copy these build prompts into Claude, Cursor, or your AI coding tool. Create a free account to unlock the full research behind them.

1. 1. Project Setup

   Build the weekend MVP of "Tendly": a small business enters its industry codes and certifications once, and a daily scan of SAM.gov shows the contracts it can actually bid on, ranked by fit and deadline.
   
   Stack: Next.js (App Router), TypeScript, Tailwind, Supabase (Postgres, Row Level Security, Auth with email magic link), the SAM.gov Opportunities API for postings, the Anthropic API to judge fit. A Vercel Cron route runs the scan. Deploy on Vercel.
   
   Tables (Row Level Security on; a user reads only their own profile and matches, and opportunities are read-only to signed-in users):
   - profiles(id, user_id, naics_codes text[], certifications text[], state, capability_statement)
   - opportunities(id, notice_id, title, agency, naics, set_aside, response_deadline, description, posted_at, url) notice_id is unique
   - matches(id, user_id, opportunity_id, fit_score, eligible boolean, reason, missing_requirements text[], status)
   - scan_runs(id, started_at, finished_at, fetched integer, errors jsonb)
   
   Screens: /login, /profile, /matches (ranked, with days left), /matches/[id] (the reason and the missing requirements).
   Env vars (names only): NEXT_PUBLIC_SUPABASE_URL, NEXT_PUBLIC_SUPABASE_ANON_KEY, SUPABASE_SERVICE_ROLE_KEY (server only), SAM_API_KEY, ANTHROPIC_API_KEY, CRON_SECRET.
   
   Do not build: billing, plans or an alerts add-on, Grants.gov or state portals, a Playwright scraper, embeddings, email or SMS alerts, proposal writing.
   Done when: npm run dev starts, you can sign in, and the four tables exist with Row Level Security on.

2. 2. Core Feature

   Build the one feature that proves Tendly: a scan that finds real postings and says plainly why each one fits or does not.
   1. A cron route at /api/scan (protected by CRON_SECRET, also callable from a Run now button) reads the NAICS codes from every profile, then fetches postings from the SAM.gov Opportunities API for those codes since the last run, using its posted-from and posted-to date parameters.
   2. Upsert each posting into opportunities by notice_id and keep the deadline, set-aside and description.
   3. For each profile, take the postings with an overlapping NAICS code and a future deadline. Check the set-aside in plain code first: if it requires a certification the profile lacks (8(a), HUBZone, service-disabled veteran or women-owned), mark the match not eligible and skip the model.
   4. For the rest, send the posting text and the profile to the Anthropic API with a strict JSON schema { fit_score: number from 0 to 1, eligible: boolean, reason: string, missing_requirements: string[] }. Save a match for any fit_score above 0.6.
   5. /matches lists matches by days left, then fit. Each shows the agency, the deadline, the fit score as a number and the reason in one sentence.
   6. A rate limit or an error from SAM.gov retries with backoff and is recorded in scan_runs.errors. It never fails the whole run.
   Rules: the model sees the posting text and the profile, nothing else. Say plainly that fit is a suggestion and the solicitation is the source of truth. Link to the posting on SAM.gov from every match.
   Empty state: with no profile, show the profile form. With a profile and no matches, show the last scan time.
   Done when: a profile with one NAICS code and no certifications scans real postings, an 8(a)-only posting is excluded without a model call, matches above 0.6 show with their reasons, and a forced 429 retries and the run still finishes.

3. 3. Landing Page

   Build a one-page landing site for Tendly, a government contract matcher for small businesses.
   Hero: "The government already wants to buy from you. Make sure you see it in time." Sub: "Enter your industry codes and certifications once. We scan the federal postings every day and show only the contracts you can bid on." One button: Join the waitlist.
   Sections: the problem (small businesses miss set-asides written for them because nobody watches the portal), how it works in four steps (profile, scan, match, deadline), a sample match card with a fit score, a reason and the missing requirements, a placeholder for what a capture manager costs (fill in a figure you can cite), and an FAQ on how fresh the data is, how fit is scored and where to register on SAM.gov.
   Waitlist: store the email in a waitlist table in Supabase. No other service.
   Style: Geist, an off-white background, near-black type, one lime accent.
   Done when: the page renders on a phone and a submitted email appears in the waitlist table.

4. 4. Branding Package

   Use a design or image tool for this one. A coding agent cannot draw a logo.
   Brand for Tendly: a wordmark and an icon that suggest a notice with a check at its corner.
   Colors: near-black, off-white and one lime. Type: Geist, with tabular numbers for scores and dates.
   Deliverables: wordmark, icon, three fit bands (strong, possible, long shot) that differ by shape and number as well as color, a match card layout, and one launch graphic.
   Done when: each deliverable is saved in one folder and the fit bands are distinguishable without color.