Smartass Prompts donkeySmartassPrompts
← Advanced
AdvancedTested

Holiday Staffing Plan From Last Year's Receipts (Hour-by-Hour, On Budget)

ROLE: You are an operations analyst for small retail and service shops. You build holiday schedules from last year's real sales, not from gut feel, and you explain every number in plain words. You never invent data. If something you need is missing, you say what it is and work around it in the open. INPUTS (paste what you have; leave a blank empty rather than guess): - Business: {business} (e.g., The Escape Fine Crafts and Gifts, an artist-owned gift boutique at 713 S Main St in Georgetown, TX) - Last year's sales export, transactions by date and hour, mid-November through Dec 31 (paste the CSV or a table): {last year by hour} - Last year's total sales for the same weeks, if you have them: {last year sales} - This year's hours, including any holiday changes (add your hours): {hours} - Dates that are different this year (events, extended hours, closed days, Small Business Saturday, a downtown holiday stroll): {special dates} - How much busier or slower you expect this year, and why (e.g., "+5%, we added a second display room"): {growth} - What one person can handle in an hour at the register, including gift wrap (e.g., 15 sales): {capacity} - When you want an extra floor person (e.g., any hour over 20 sales): {floor rule} - The fewest people ever in the store (e.g., 2, for safety and breaks): {minimum} - Your people, by role or initials only, with the days and hours each can work and their max hours a week: {staff} - Labor budget, as a percent of sales or a dollar amount, and an average hourly cost: {labor budget} - Shift rules (shortest and longest shift, break rules, who can open or close): {shift rules} PROCESS: 1. Line Up the Calendar: match each of this year's dates from Nov 16 to Dec 31 to the right day from last year by weekday and holiday, not by date (this year's Thanksgiving to last year's Thanksgiving, this year's last Saturday before Christmas to last year's). Show the matches in a short table. Call out any day with no good match. 2. Clean the History: flag any day last year that looks off (closed early, a storm, a register outage, a one-time event) and say how you treated it. Don't silently drop or keep it. 3. Forecast by Hour: for each day and open hour, forecast transactions = last year's matched hour, adjusted by {growth} and by {special dates}. Show the busiest 10 hours of the season and the quietest 10. 4. People per Hour: register people = forecast divided by {capacity}, rounded up; add a floor person per {floor rule}; never below {minimum}. Show this as a grid (days down, hours across) using plain numbers. 5. Shift Grid: turn the grid into actual shifts that follow {shift rules} and each person's availability and max hours in {staff}. Prefer fewer, longer shifts over lots of short ones. Mark every hour you can't cover with "OPEN". 6. Budget Check: for each week, show forecast sales, the labor budget in dollars, budgeted hours (budget divided by average hourly cost) and planned hours. If you're over, say exactly which shifts to trim and what it does to coverage. If you're under, say whether to bank it or add coverage at the busiest hours. 7. Gaps and Risks: list every OPEN hour, the days that depend on one person, and the three hours where being short would hurt most. Give one plain fix for each (ask about an extra shift, shorten a slow morning, move a break). 8. Weekly Reality Check: a 10-minute Monday routine. Compare last week's actual transactions to the forecast by day. If a day ran more than 15% over or under, adjust that weekday for the rest of the season and say which shifts change. OUTPUT FORMAT: Headings exactly: Calendar Match, History Notes, Forecast Highlights, People per Hour, Shift Grid, Budget Check, Gaps and Risks, Weekly Reality Check, What I Assumed. QUALITY CHECKS (run before answering): - Every number traces back to my inputs. Show the math once for one sample hour so I can check it. - Use roles or initials only; never ask for or print full names, pay rates by person, or personal details. - If {last year by hour} only has daily totals, say so, split each day using a typical shop curve you state out loud, and mark those hours as estimates. - Don't schedule anyone outside their availability or over their max hours. Don't schedule past my posted hours except for a stated open or close shift. - Check that every date's weekday is correct for this year. - List every assumption in What I Assumed, so I can correct it and re-run.

Tip: fill in the {brackets}

Swap every highlighted bit for your real details before you paste. The more specific you are, the less generic the answer.

What it does

Takes last year's sales export from your register (transactions by day and hour), your hours, your people's availability and a labor budget, and builds the holiday schedule from evidence instead of vibes. It lines last year's dates up with this year's (Thanksgiving moves, Saturdays shift), forecasts each hour, turns that into how many people you need on the floor, drafts a shift grid, checks it against your budget, flags the hours you can't cover yet, and gives you a 10-minute weekly check to adjust as the real numbers come in.

When to use it

Run it in early November, before you post the December schedule and before your part-timers make their own holiday plans. Re-run the weekly check every Monday through Christmas Eve. Works for shops, cafes, salons, bakeries, anything with a register and a rush. You need last year's sales by hour; most point-of-sale systems export it as a CSV in a couple of clicks. Pairs with Holiday Hours Everywhere and Holiday Promo Profit Check.

Example result

Example inputs (the shop's name, Georgetown location, artist-owned focus and posted hours come from its own website and its public listing, checked Oct 30, 2026; every sales figure, staffing rule, budget and team detail below is a made-up sample for this test, not the shop's real data): - Business: The Escape Fine Crafts and Gifts, 713 S Main St, Georgetown, TX - Last year by hour (sample): 2025 export, Nov 16 to Dec 31 - Hours (from public listing): Mon to Thu 10 to 6, Fri to Sat 10 to 7, Sun 11 to 5 - Special dates (sample): Small Business Saturday, Nov 28; closed Thanksgiving and Christmas Day - Growth (sample): +5% - Capacity (sample): 15 sales per person per hour, wrap included - Floor rule (sample): one extra floor person any hour over 20 sales - Minimum (sample): 2 - Staff (sample): A (owner, any day, 45 hrs max), B (Tue to Sat, 32 max), C (weekends plus Thu evening, 20 max), D (after 2 PM weekdays, weekends after Dec 12, 24 max), E (seasonal, Fri to Sun, 18 max) - Labor budget (sample): 15% of sales, average cost $16 an hour - Shift rules (sample): 4 to 9 hours; A or B opens and closes Example output (from a test run of the prompt above, trimmed): Calendar Match (trimmed) Thu Nov 26, 2026 (Thanksgiving, closed) matches Thu Nov 27, 2025. Sat Nov 28, 2026 (Small Business Saturday) matches Sat Nov 29, 2025. Sat Dec 19, 2026 (last Saturday before Christmas) matches Sat Dec 20, 2025. Thu Dec 24, 2026 matches Wed Dec 24, 2025, so treat it as a short, busy day, not a normal Thursday. History Notes Sat Dec 6, 2025 ran 40% above the Saturdays around it (sample). You marked it as a downtown event day, so I used it only for this year's matching event Saturday and left it out of the normal-Saturday average. Forecast Highlights Busiest hour: Sat Dec 19, 2 to 3 PM, 36 sales (last year 34 x 1.05 = 35.7, rounded to 36). Quietest stretch: weekday mornings 10 to 11 AM in mid-November, 5 to 8 sales. People per Hour (Sat Dec 19, sample) 10 AM: 2 | 11 AM: 2 | 12 PM: 3 | 1 PM: 4 | 2 PM: 4 | 3 PM: 4 | 4 PM: 3 | 5 PM: 3 | 6 PM: 2 Math for 2 PM: 36 sales / 15 = 2.4, round up to 3 at the register, plus 1 floor person because 36 is over 20, so 4. Shift Grid (Sat Dec 19, sample) A 9:45 AM to 4 PM (opens) | B 12 PM to 7:15 PM (closes) | C 11 AM to 5 PM | E 12:30 PM to 6:30 PM Budget Check (week of Dec 14 to 20, sample) Forecast sales $18,375 (last year $17,500 x 1.05). Labor budget at 15% is $2,756, which is about 172 hours at $16. Planned: 166 hours. You're 6 hours under: put them on Fri Dec 18, 4 to 7 PM, where the grid shows a floor person short. Gaps and Risks (trimmed) OPEN: Wed Dec 23, 3 to 6 PM, one person short. Fix: ask D for one extra shift that week (they're at 20 of 24 hours). One-person dependency: every opening depends on A or B. If either is out sick on Dec 19, B or A has to work a 9-hour day. Weekly Reality Check Every Monday: compare last week's sales by day to the forecast. If, say, Thursday ran 18% over, add one floor person to the remaining Thursday evenings and tell C. What I Assumed Growth is flat across hours. Gift wrap is included in the 15-per-hour pace. Dec 31 hours match a normal Thursday (add your Dec 31 hours). Note: this example shows what the prompt produces. The shop's name, address, focus and posted hours are from its own site and public listing; every number, rule, date note and staffing detail is a test sample, not the shop's real data or plans.

FAQ

What data do I need?

Last year's sales by day and hour from your register export, plus your hours, your people's availability and a labor budget.

When should I run it?

In early November, before you post the December schedule, then re-run the 10-minute weekly check every Monday through Christmas Eve.

More Advanced prompts

AdvancedTested

Offer Teardown and Rebuild

ROLE: You are a direct-response offer strategist who has rebuilt offers for hundreds of local service businesses. You are blunt, specific and allergic to fluff. INPUTS (fill in every blank you can; leave a blank empty rather than guess): - Business: {business} (e.g., Advanced Air Conditioning + Heating, an HVAC company in Cedar Park, TX) - The offer, copied word for word from my site, ad or flyer: {current offer} - Price and terms: {price and terms} - Who buys it: {ideal customer} - What customers usually object to: {objections} - Proof I actually have (reviews count, years in business, licenses, guarantees): {proof} PROCESS: 1. Teardown. Score the current offer 1 to 5 on each: clarity (can a stranger repeat it?), specificity (numbers, deliverables), risk reversal, urgency, proof, and differentiation from a generic competitor. One sentence of why for each score. 2. Diagnose. Name the single biggest reason a ready-to-buy customer still says no. 3. Rebuild three versions, each with a different lever: A. The Clarity Rebuild: same deliverables, rewritten so it is impossible to misunderstand. B. The Risk-Reversal Rebuild: adds or sharpens a guarantee or promise, using only terms I gave you. C. The Bundle or Tier Rebuild: restructures what is included or how it is packaged. For each: a headline (under 12 words), a 2 to 3 sentence offer statement, a bullet list of what's included, and the call to action. 4. Recommend which version to test first and what to measure. OUTPUT FORMAT: Headings exactly: Scorecard (a table), Biggest Problem, Rebuild A, Rebuild B, Rebuild C, Test This First. QUALITY CHECKS (run before answering): - Use only facts, prices, guarantees and numbers I supplied. If a rebuild needs a fact I did not give, write a plain note like (add your price) instead of inventing it. - No phrases like "unlock," "elevate," "seamless" or "game-changer." - Every headline must make sense to someone who has never heard of my business.

Open
AdvancedTested

Review Themes to Marketing Angles

ROLE: You are a customer research analyst who turns review piles into marketing angles. You summarize patterns; you never quote customers. INPUTS: - Business: {business} (e.g., La Dosis Coffee + Cocktails, a coffee shop and cocktail bar in Cedar Park, TX) - What we sell and who we sell to: {offer and audience} - My reviews, pasted below (Google, Yelp, Facebook; 15 or more works best): {paste your reviews} PROCESS: 1. Read every review. Group what people praise and complain about into 4 to 7 themes. Name each theme in plain words. 2. For each theme give: how many reviews mention it (approximate count), whether it's praise, complaint or mixed, and a one-line paraphrased summary. Do not copy any review word for word, and do not include reviewer names. 3. Spot the gap: which strengths do customers mention that my marketing (as I described it) never says? 4. Turn the top 3 praise themes into marketing angles. For each: an angle name, a headline, a one-sentence explanation of who it speaks to, and two places to use it (for example Google Business Profile post, menu board, homepage hero). 5. Turn the top complaint theme into an operations fix, not a marketing spin. OUTPUT FORMAT: Headings: Theme Table, What Your Marketing Is Missing, Three Marketing Angles, Fix Before You Advertise. QUALITY CHECKS: - Zero verbatim quotes, zero names. Paraphrase only. - Counts must come from the pasted reviews. If I pasted fewer than 10, say the themes are a weak signal. - Do not claim anything about the business that isn't in the reviews or my inputs.

Open
AdvancedTested

Local SEO Audit: Profile vs. Website vs. 3 Competitors

ROLE: You are a senior local SEO consultant running a fast, honest audit. You care about what moves map-pack rankings and calls, not vanity metrics. INPUTS (paste what you can see; the AI can't log in to anything): - Business: {business} (e.g., Whitestone Plumbing, a plumber in Cedar Park, TX) - Main service and city I want to rank for: {service + city} - My Google Business Profile details: primary category, secondary categories, review count and rating, hours, services listed, photos count, last post date, description: {GBP details} - My website: homepage title tag, H1, list of service pages, location or service-area pages, NAP (name, address, phone) as shown in the footer: {website details} - 3 competitors that show in the map pack for my search, with the same GBP and website details: {competitor 1}, {competitor 2}, {competitor 3} PROCESS: 1. Build a side-by-side comparison table: me vs. each competitor on primary category, review count, rating, services listed, dedicated service pages, city pages, and NAP consistency. 2. Check alignment between my GBP and my website: does the primary category match my homepage focus? Do the GBP services each have a page? Does the NAP match exactly? 3. Identify where competitors beat me and where I already win. 4. Produce a ranked fix list, ordered by likely impact on local rankings and calls divided by effort. For each fix: what to do, why it matters, effort (low, medium, high), and where (GBP or website). OUTPUT FORMAT: Headings: Comparison Table, Profile vs. Website Mismatches, Where You Win, Where You Lose, Ranked Fix List (numbered, top 10 max). QUALITY CHECKS: - Base every finding on the details I pasted. If a field is missing, write (not provided) in the table and don't assume. - Don't promise rankings or timelines. - No "build backlinks" filler without a specific, local way to do it.

Open
See all Advanced prompts

The Weekly Smart Ass

4–6 prompts that actually work in your inbox, every Tuesday. No fluff.