On the Idea Wall · ▲ 0 votes
JobSift — the spec
An internal tool for solo business owners who receive job opportunity emails and want to stop managing them manually. JobSift connects to a designated Gmail label, scans every email and its linked pages for job postings, and writes structured opportunity records into a Google Sheet — company, position, deadline, salary range, and direct link — keeping the sheet current and free of duplicates without the user touching it.
---
Decisions locked
| Question | Answer |
|---|---|
| Shape | Internal tool (single-user, no multi-tenant UI required) |
| Audience | Solo business owners |
| Core loop | Discover new opportunities passively through automated email extraction |
| Success metric | A curated, accurate job list exists in a Google Sheet within 30 days of setup |
---
The core loop
- User assigns a Gmail label (e.g. "Jobs") to incoming emails containing job leads — manually or via a Gmail filter they already run.
- JobSift runs on a schedule, pulls all unprocessed emails under that label, and extracts body text plus every outbound link.
- Each link is fetched and scored for job-posting signals (role title, apply button, deadline language, compensation figures).
- Confirmed postings are written as new rows in the linked Google Sheet; duplicates detected against existing rows are silently skipped.
- The Sheet populates five fields per row: company, position, application deadline, salary or salary range, and posting URL.
- As deadlines approach, the tool fires an email or SMS alert so no deadline is missed.
---
v1 scope
Gmail label selector and email batch processor
A configuration step where the user picks the target Gmail label; the processor then fetches all emails in that label in batches, marking each as processed after extraction. Lives on the Setup screen.
Link extraction and job posting detection
Every email body and embedded URL is parsed; linked pages are fetched and run through a classifier that distinguishes job postings from newsletters, footers, and noise. Runs as a background service with no dedicated UI beyond a processing log.
Google Sheet auto-population with five key fields
Confirmed job postings are appended to a connected Sheet with columns for company, position, application deadline, salary or salary range, and posting URL. Operates on the user's own Google Sheet via OAuth; the Sheet is the primary output surface.
Application deadline countdown and alerts
Deadlines extracted from postings are tracked; configurable thresholds (e.g. 7 days, 3 days, 1 day before) trigger an email or SMS notification. Configured on the Alerts screen, delivered outside the app.
Duplicate job detection across emails
Before writing a row, the tool compares the posting URL and company-plus-position pair against existing Sheet rows. Exact and near-matches are suppressed; a deduplicated count is surfaced in the run summary log.
---
Deliberately later
- Salary range parsing and normalization — raw salary strings vary wildly across postings; a normalization layer needs a corpus of examples the tool will only accumulate after real use.
- Manual edit sync back to sheet — round-tripping user edits requires conflict resolution logic; the v1 sheet is append-only, which is safe and predictable.
- One-click apply link preservation — some postings gate applications behind login walls; handling that reliably requires session management that outscopes v1 extraction.
---
Data model sketch
runs— run_id, triggered_at, label_name, emails_scanned, postings_found, duplicates_skipped, statusprocessed_emails— email_id (Gmail message ID), run_id, processed_at, postings_extracted_countraw_links— link_id, email_id, url, fetch_status, is_job_posting (bool), fetched_atjob_postings— posting_id, link_id, company, position, deadline, salary_raw, posting_url, sheet_row_id, created_atduplicates_log— duplicate_id, incoming_posting_id, matched_posting_id, match_reason, suppressed_atalerts— alert_id, posting_id, threshold_days, channel (email/SMS), sent_at, statusconfig— user_id, gmail_label, sheet_id, alert_email, alert_phone, schedule_cron
---
Screens
- Setup — connect Gmail OAuth, pick target label, connect Google Sheets OAuth, point to or create the destination Sheet.
- Dashboard — last run summary: emails scanned, postings added, duplicates skipped, next scheduled run.
- Processing log — per-run history with expandable detail on each email and link outcome.
- Alerts config — set deadline thresholds, choose email or SMS, enter contact details.
- Google Sheet (external) — the live output; all five fields visible and sortable by deadline.
---
How to use this document
- Bring it into Mind Palace, where the guided platform and its AI coach pick up from exactly this document and build the tool with you step by step.
- Hand it to a developer as the complete v1 brief — scope, data model, and screen list are all here.
- Keep it as the single source of truth during the build so every decision traces back to one place.
This is Yvette's. Build yours.
A spec like this is step 3 of Mind Palace's nine — the other six take a weekend: working software, a real offer, first customers.
Want to build this with Yvette?
Tell us who you are and we'll broker the introduction — their contact details stay private until they say yes.