Real shapes of work, real URLs

Prompt: “Our inbound leads come from a few places (the website contact form, a pricing-page “request a quote” button, and referrals) and they scatter across inboxes, so we follow up slowly. Stand up one webhook endpoint our forms can post to, capture every submission (name, email, company, source, message, and an estimated value), and keep the full history so nothing is lost. The moment a lead arrives, post a clean, readable alert to our sales channel with those fields and a link, and text whoever is on call when the estimated value is above a threshold I’ll set. Give us a private inbox view to triage leads by status, and let me change the routing later without the webhook URL ever changing.”

Prompt: “We run a small SaaS and too often hear about outages from customers before we catch them ourselves. Build an uptime monitor for our production surfaces: marketing site, app, API, checkout, and docs (I’ll paste the exact URLs). Check each on a schedule (every 60 seconds), record the status code and response time, and keep the history. Treat two consecutive non-2xx checks as down, and flag a “degraded” state when a URL is up but slow (over ~1.5s). When something goes down, alert our team channel with the endpoint, the failing status, and how long it has been failing, then alert again when it recovers. Publish a clean public status page at its own URL with each service’s current state, 90-day uptime, and an incident log, and keep it private until we’re ready to share it.”

Prompt: “We want to test demand for a new product before we commit engineering time, so we need a real landing page we can start driving traffic to today. Build a fast, polished page that explains the offer with a clear headline and three concrete value points (I’ll give you the product details), captures emails with a single form, and shows a friendly confirmation with the person’s spot in line. Store the signups so we can export them, reject duplicate and obviously-fake addresses, and give us a private running count. Make it feel like a real brand rather than a template, look right on mobile, and hand back a public URL we can share plus a private draft state until we flip it live.”

Prompt: “We keep missing changes on pages that matter to us: a competitor’s pricing, a supplier’s catalog, and a couple of job boards we recruit from. Build a watcher that checks the pages I give you on a schedule (a few times a day), detects meaningful changes rather than layout noise, and keeps a dated history of what changed with a clear before/after. When something material moves (a price changes, a role we care about is posted) alert our team channel with a short summary of exactly what changed and a link. Give us a private dashboard showing each watched page, when it was last checked, and its recent changes, and let me define what counts as “meaningful” per page.”

Prompt: “Our ops team loses hours every week hand-cleaning the same messy CSV exports (duplicate rows, inconsistent casing, stray spaces, broken email addresses, half-empty rows) and mistakes still slip through. Build a private web tool where we upload a CSV and it detects those issues and shows a count of each, then previews a clean before/after side by side. Let us toggle each fix (dedupe, trim whitespace, normalize casing, flag or drop bad emails, remove empty rows), map or rename columns to our standard headers, and export a clean file that’s ready for our CRM. It has to handle our real exports (a few thousand rows), process everything in the browser so our data never leaves, and be usable by non-technical teammates: a reusable tool, not a one-off script.”

Prompt: “We bill a handful of clients and every invoice and quote is a copy-paste from the last document: numbering drifts, totals and tax get fat-fingered, and it looks inconsistent. Build a private tool where I enter a client, line items, quantities, rates, and a tax rate, and it generates a clean, correctly-numbered invoice or quote as a downloadable PDF with our name, logo, and payment details. Do the totals and tax math for me, keep every issued document in a searchable list, and never reuse or skip a number. Make it fast to reissue a similar invoice next month, and keep it on-brand rather than a generic template.”

Prompt: “I’m always hunting for a good price on specific telescopes and eyepieces, but the real deals sell out before I notice. Watch the retailers and marketplace listings I give you on a schedule, track each model’s price over time, and alert me the moment one drops below my target or hits a new low, with the store, the current price, and a link. Keep a price history so I can tell whether a “sale” is actually a good deal versus its recent range, publish a deals page I can check anytime, and let me add or remove models as my wishlist changes.”

Prompt: “We run workshops and all-hands where we want the room to vote and see results update live on the screen. Build a full-stack polling app where I create a question with options, share a link or short code for people to vote from their phones, and show results updating in realtime as votes arrive: a bar per option with a running count. Prevent obvious double-voting, let me open and close a poll, and keep past polls so we can revisit results. Hand back a public voting URL and a private host view to run the session.”

Prompt: “Our product docs are a folder of markdown files engineers keep up to date, but customers have nowhere good to read them. Turn that folder into a fast, clean documentation site with a sidebar built from the file structure, full-text search, syntax-highlighted code blocks, and deep links to any heading. Keep it in sync when we update the markdown, make it readable on mobile, and publish it at its own URL we can point our support articles at.”

Prompt: “We track stock in a spreadsheet nothing else can talk to, so counts drift and reorders run late. Build an inventory tracker with a simple UI to add products, adjust quantities, and set a reorder threshold per item, backed by a REST API our other tools can call to read and update stock. Show what’s low or out, log every change with who and when, and let us export the current state. Keep it private to our team behind a login.”

Prompt: “I have a resume but no personal site, and I want one link to put on applications and profiles. Build a clean, fast portfolio site from my resume (I’ll paste it): a short intro, selected work or projects with a line on each, skills, and contact links. Make it tasteful and readable rather than a template, work well on mobile, include basic SEO and social-preview tags, and give me a URL I can share.”

Prompt: “We ship constantly but customers can’t tell what changed, and nobody has time to write release notes. Each week, take our merged git commits (I’ll connect the repo), group them into user-facing themes (new, improved, fixed) and draft a readable changelog entry in plain language, skipping internal noise. Publish it to a public changelog page grouped by date, let us edit an entry before it goes live, and keep the history at a stable URL customers can follow.”

Prompt: “Vendor invoices land in our inbox and someone re-types them into our books days later. Watch a dedicated inbox for incoming invoices, extract the vendor, invoice number, date, line items, tax, and total from the PDF or body, and append a clean row per invoice to our bookkeeping sheet. Flag anything it isn’t confident about for a human to confirm rather than guessing, never enter the same invoice twice, and send a short weekly summary of what was captured.”

Prompt: “New signups arrive with just an email, so our CRM fills up with thin, duplicate records. When a lead comes from our signup form, enrich it with company and role details, normalize the fields, and check it against existing records so we merge instead of duplicating. Then sync a clean record into our CRM with the source and signup date, and route anything that looks fake or role-based (like info@) to a separate review list rather than the pipeline.”

Prompt: “Our key numbers are spread across a few sources and nobody assembles them, so Monday planning runs blind. Every Monday at 7am, pull our weekly metrics (I’ll connect the sources): signups, revenue, active users, whatever we choose. Compare them to the prior week and the trend, and email the team a clean summary with the highlights and any big moves called out. Keep each week’s snapshot so we can look back, and let me change which metrics are included.”

Prompt: “I’m planning a trip and fares for my route swing every day, but I only notice after the cheap window closes. Watch fares for my route and date range on a schedule, keep a history so I can see the trend, and alert me the moment the price drops below a target I set, with the current fare and how it compares to what I’ve seen. Let me watch a couple of routes at once, and tell me when a price is unusually low versus its recent range, not just below the number.”

Prompt: “I’m job hunting and the roles I want fill up before I see them. Watch the job boards and company pages I care about for postings that match my filters: title, location or remote, and keywords. Check on a schedule, and ping me with only the new matches, each with the title, company, and a direct apply link. Remember what it has already shown me so I don’t get repeats, and keep a running list I can review of everything it has found.”

Prompt: “I have a wishlist of products I’d buy at the right price, but I never catch the drops. Track the price of each item across the stores that carry it on a schedule, keep a price history, and alert me when one falls below my target or hits a new low, with the store, the current price, and the link. Show each item’s recent price range so I know whether a “sale” is actually a good deal, and let me add or remove items easily.”

Prompt: “Our pricing page is where people decide to buy, and right now it undersells us. Build a clear pricing page with three tiers, a monthly/annual toggle that shows the annual savings, a highlighted “most popular” plan, and a feature comparison that’s easy to scan. Add a contact-sales CTA for the top tier and a short FAQ that handles the usual objections (I’ll give you the plans and features). Make it polished and on-brand, load fast, read well on mobile, and hand back a URL we can ship.”

Prompt: “People find our restaurant on their phone and just want the menu, hours, and a way to order. Our current page makes that hard. Build a simple, good-looking site with menu sections and prices, today’s hours (and holiday exceptions), our address with a map, and a prominent call-to-order button that dials or links to ordering. Make it fast and mobile-first, easy for us to update when the menu changes, and give us a URL to put on our listings and receipts.”

Prompt: “We’re running an event and attendees keep asking who’s speaking when and how to register. Publish a conference microsite with a day-by-day, track-by-track schedule, speaker cards with bios and photos, session details, venue and travel info, and a clear register button. Make the schedule easy to filter, readable on a phone in a hallway, simple for us to update as the lineup firms up, and live at its own URL we can promote.”

Prompt: “We have open roles but nowhere presentable to send candidates, so good people bounce. Turn our list of openings (I’ll paste them) into a careers page with a short pitch for working here, roles grouped and filterable by department and location, and each job on its own page with the description and a clear apply link. Make it on-brand and fast, easy for us to add or close a role, and live at a URL we can link from job posts and our site.”

Prompt: “We ship improvements every week but customers never hear about them. Ship a public changelog that reads from our release-notes markdown, renders each entry with a title, date, and tags (new, improved, fixed), and groups them by month on a clean timeline. Support images and code snippets in entries, stay in sync when we add notes, read well on mobile, and live at a stable URL we can link and let customers follow.”

Prompt: “Our front desk schedules by phone, which wastes time and leads to double-bookings. Build a booking app where a patient picks a provider, sees only real open slots, chooses a time, and gets an email confirmation, with the slot locked so it can’t be double-booked. Let staff set each provider’s availability and block time off, send a reminder before the appointment, and give patients a link to cancel or reschedule. Keep patient details private behind a login, with a private admin calendar for the team.”

Prompt: “We reconstruct billable hours from memory at invoice time, and money leaks. Build a time-tracking app where team members log hours against a client and project with a note, using a running timer or manual entry, and see their week at a glance. Give managers a view of hours by client, project, and person, the ability to approve entries, and a weekly export ready for invoicing. Keep it behind a team login with roles for members and managers.”

Prompt: “Purchase requests bounce around email with no clear owner or record. Build a PO approval app where someone submits a request with vendor, line items, amount, and reason; it routes to the right manager based on the amount; and everyone can see its status (submitted, approved, or rejected) with comments. Email the requester on a decision, keep a full audit trail of who approved what and when, and give finance a view of open and approved POs to export. Keep it behind a team login with an approver role.”

Prompt: “Our team’s knowledge is scattered across chats and docs, and nobody can find it later. Build an internal wiki where we write pages in markdown, organize them into sections, and search the full text instantly. Keep version history so we can see what changed and who changed it, support links between pages and images, and put the whole thing behind a login for our team only. Give us a clean reading view and a fast editor.”

Prompt: “Every billing question (change my plan, update my card, resend an invoice) turns into a support ticket. Build a secure customer portal where a signed-in user sees their current plan and renewal date, can upgrade, downgrade, or cancel, update their payment method, and download past invoices. Connect it to our billing (Stripe), reflect changes accurately, handle failed payments gracefully, and scope everything so a user only ever sees their own account.”

Prompt: “We don’t have a reliable backup routine, so we’re one bad migration from losing data. Every night at 2am UTC, take a compressed dump of our Postgres database, upload it to our S3 bucket with a dated filename, and delete dumps older than 14 days so storage stays bounded. Verify each dump completed and is non-empty, alert us if a backup fails or is skipped, and keep a short log of recent runs so we can confirm at a glance that backups are current.”

Prompt: “An expired TLS certificate takes our site down, and it always seems to happen on a weekend. Check our production domains (I’ll list them) once a day, read each certificate’s expiry, and email the team 14 days before any of them expires, then again at 3 days if it still hasn’t been renewed. Include the domain, the exact expiry date, and the issuer, and give us a simple dashboard showing every domain and its days remaining so nothing slips.”

Prompt: “Our store and our books drift apart, so month-end reconciliation is a slog. Every hour, pull new Shopify orders and push each into our accounting system as a clean record with line items, discounts, shipping, and a tax breakdown, matched to the right customer. Skip orders already synced so nothing is duplicated, handle refunds and cancellations, and alert us on any order it couldn’t sync with the reason. Keep a log of what synced each run.”

Prompt: “We find out about the article or post that mattered days after it’s up. Each morning, scan news and social feeds for mentions of our company and product names (and a couple of key people), and email me one digest grouped by source with the headline, a one-line summary, sentiment, and a link for each. Filter out obvious noise and repeats, put anything high-reach or negative at the top, and keep the past digests so we can look back.”

Prompt: “Abandoned tickets pile up and bury the ones that actually need a reply. Every night, find support tickets with no customer response in 30 days, post a friendly final notice that we’ll close it unless they reply, wait a few days, and close the ones still idle with a clear reason. Never touch tickets that are waiting on us or marked important, log every action taken, and send the team a short summary of what was noticed and closed.”

Prompt: “Receipts get lost in people’s camera rolls and expenses are reconciled from memory. Build a tool where a team member uploads or snaps a receipt photo, it reads the vendor, date, total, and tax, lets them confirm or fix the fields and pick a category, and appends a clean row to our expenses sheet with a link to the image. Handle blurry or partial receipts by asking for a quick confirm rather than guessing, and give managers a running view of submitted expenses.”

Prompt: “When a service is degraded, the team finds out late in a noisy channel. Stand up an internal status page showing each of our APIs and workers as operational, degraded, or down from real health checks, with current response times and recent uptime. Let us post incident notes with a timeline and updates, let teammates subscribe by email to changes for services they care about, and keep an incident history. Publish it at a private URL for the team.”

Prompt: “Our campaign links are long, untracked, and made one at a time. Build a URL shortener our team can use in bulk: paste a list of destination URLs (with optional custom slugs and campaign tags), get short links back, and track click counts, referrers, and clicks over time per link. Let us search and filter our links, group them by campaign, and export the stats. Keep it behind a team login so the links and analytics stay ours.”

Prompt: “We make each contract by copy-pasting the last client’s document and hoping we caught every field. Build a form that captures the client and deal details (name, dates, scope, amounts), fills our standard contract template, and returns a clean, correctly formatted PDF ready to send. Validate the inputs so nothing is left blank, keep the template easy for us to update in one place, and save a copy of each generated contract for our records. Keep it private to our team.”

Prompt: “Debugging a webhook means waiting for the provider to fire it again and hoping we catch it. Build a tool that gives us a capture URL, records every incoming webhook with its headers, payload, and timestamp, and lets us inspect any one in a readable view. Let us replay a captured request to our local or staging endpoint on demand, filter and search past events, and keep a rolling history. Keep the capture endpoint private to our team.”