Skip to content
Wishdeal Factory Commission a build
Wishdeal Factory
Foreman feed · cross-LLM critiques

2408 reports, 36039 demands shown.

The Foreman runs Claude and Codex in parallel against the 12-site quality reference corpus, producing a numbered list of demands per product. This page surfaces the demands so the studio's harshest critic is browsable without opening every file.

bookkeeper-ai

Aug 29, 13:07 · 10KB · 15 demands shown
  1. 1. Strip `border-left: 4px solid #1db87a` from both `.card` and `.testimonial` -- left accent bars appear on every card and every testimonial block, which is an explicitly banned pattern per studio standards.
  2. 2. Replace Plus Jakarta Sans headers with Fraunces -- the brand tokens declare `--wd-brand-font-display: 'Plus Jakarta Sans'` with no documented variation; the studio standard is Fraunces serif for display or a written-down exception.
  3. 3. The body CSS sets `font-family: 'Plus Jakarta Sans'` globally, overriding the Inter declaration in the brand token block -- Inter must actually render for body copy, not just appear in a variable that nothing uses.
  4. 4. The palette is navy `#0f1f3d` plus mint `#1db87a` with zero gold and zero cream -- bring in at least one warm neutral or file a documented deviation; the current combination reads generic fintech, not studio quality.
  5. 5. The hero is a centered-text dark gradient with no real photograph above the fold -- proxybox.us puts a product screenshot in the hero; a bookkeeping AI product needs to show either the UI or a photo of the actual work context (a desk, a rec
  6. 6. The headline "Your books, done by morning" names neither who it's for nor what specifically changes -- rewrite to land on the freelancer or solo consultant with a concrete pain hook, e.g. "Stop reconciling your own bank feed" or "Your bank
  7. 7. Hero subtitle text is styled `color: #a0c4ff` (light blue) -- this is a fourth color outside the declared palette that appears nowhere else on the page; replace with cream, white, or a stated palette value.
  8. 8. The visible section structure is hero / feature cards / pricing table / testimonials / footer -- that is five sections at best, below the six-section floor; add a "How it works" numbered step flow and a FAQ block at minimum.
  9. 9. The `.testimonial` elements have no name, photo, job title, or company visible in the HTML -- if these are fabricated they must be removed entirely; if real, require full attribution (first and last name, role, company type) as revoscape do
  10. 10. No security callout block exists anywhere in the structure -- a freelancer handing over bank read-access will reject the page without a single explicit statement on encryption, read-only access scope, and data retention; this is the single
  11. 11. The feature cards use `background: #f8f9fa` with no imagery -- revoscape pairs every feature block with a real environment photograph; these cards need at minimum a product UI screenshot per feature, not a gray padded box with a green left
  12. 12. No "How it works" section is present -- voicetrail uses a three-step onboarding flow with concrete verbs ("connect your bank in 60 seconds / we categorize overnight / review in the morning"); this product has a complex trust barrier that a
  13. 13. The `<header>` element is reused as the hero section while WD shell nav already occupies a `<header class="wd-shell-nav">` -- two `<header>` elements on one page is a structural accessibility error; replace the product hero with `<section>`
  14. 14. The pricing table is inline with no FAQ, no plan differentiator prose, and no explanation of what the $5 tier actually restricts -- at $199/month top tier, a stranger cannot determine what they're paying for from this page alone; each plan
  15. 15. Body word count is almost certainly under 1200 words given the sparse card structure -- a product being sold at $5-$199/month with bank-connection access needs 1200+ words to walk a skeptical freelancer through every objection before asking

bookkeeper-ai

Aug 29, 12:34 · 10KB · 15 demands shown
  1. 1. Replace every `h1`, `h2`, `h3` with Fraunces serif -- the WD_BRAND_OVERRIDE block sets `--wd-brand-font-display: 'Plus Jakarta Sans'` but that overrides the studio standard with no documented variation, so every heading renders in the wrong
  2. 2. Scrap the navy (#0f1f3d) + mint green (#1db87a) palette entirely and ship forest/gold/cream or write a one-line brand-exception note explaining why this product deliberately departs -- right now it reads like a generic fintech Bootstrap clo
  3. 3. Remove `border-left: 4px solid #1db87a` from every `.card` and every `.testimonial` -- the rule is no identical left accent bars on cards and you have applied this exact banned pattern to every content container on the page. Why: Explicitly
  4. 4. The hero is a pure CSS gradient with no photograph -- put a real Unsplash desk/finance photograph behind the hero, the way proxybox.us ships a full-bleed real image behind its headline. Why: Studio standard: real photography in EVERY hero.
  5. 5. Audit the `hero-image` element: if it is an AI-generated mockup or a blank placeholder PNG, replace it with a real dashboard screenshot or remove it entirely -- a centered 500px fake interface image is worse than no image at all. Why: Hones
  6. 6. Every testimonial is anonymous (no full name, no photo, no job title, no company) and carries the banned left accent bar -- revoscape.com has three named photos with a venue logo bar; this page needs the same treatment before it ships to an
  7. 7. The pricing section is a bare `<table>` with no CTA per row -- each tier needs its own button linking to the unlock/checkout flow, not a single link at the bottom of the table. Why: Tier 2 conversion standard; a prospect comparing plans mus
  8. 8. `Plus Jakarta Sans` is loaded three separate times in the same `<head>` (page-level preconnect+link, page-level style import, and WD_BRAND_OVERRIDE block) -- consolidate to one load and eliminate the redundant preconnect pairs. Why: Perform
  9. 9. The product's own `<header>` is a static full-viewport gradient block that sits below the shell nav -- verify that the shell's `wd-shell-nav` sticky behavior is not visually buried or z-index-conflicted by the product header on scroll, and
  10. 10. Count your visible sections: hero, features, pricing, testimonials, and footer is five -- add a numbered "How it works" section (step 1: connect your bank, step 2: review categorizations, step 3: export your report) to reach the six-section
  11. 11. The body copy does not answer the three objections a freelancer has before paying: "Is my bank supported?", "What if the AI miscategorizes?", "Where does my data go?" -- these need explicit answers in dedicated copy blocks, which will also
  12. 12. All feature card headings use `h4` in the same mint green over the same gray background with the same layout -- vendoriq.vip differentiates its feature blocks with alternating image/text layout; vary at least one card block to break the ide
  13. 13. "Import transactions, categorize automatically, generate reports in seconds" is a horizontal checklist of actions, not benefit copy -- rewrite as outcome-first: "Your tax preparer gets a clean export. You stop spending Sunday on receipts."
  14. 14. There is no FAQ section -- a freelancer buying bookkeeping AI generates at minimum six objections before they hand over a credit card; ship a FAQ section with real answers before this page goes to a prospect. Why: Tier 2 SMB standard; FAQ i
  15. 15. The hero subheadline is rendered in `color: #a0c4ff` (baby blue pastel) -- this reads as consumer tech, not professional finance; change to a warm cream or neutral that matches the product's trust positioning. Why: Palette standard; pastel

bookkeeper-ai

Aug 29, 11:07 · 11KB · 15 demands shown
  1. 1. `.card { border-left: 4px solid #1db87a }` is a left accent bar applied to every feature card - this pattern is explicitly banned; replace with a four-sided card border or subtle drop shadow.
  2. 2. `.testimonial { border-left: 4px solid #1db87a }` repeats the identical banned treatment on every testimonial block - two separate sections sharing the same forbidden stripe is not an accident, it is a design system choice; fix both at once
  3. 3. The hero is `linear-gradient(135deg, #0f1f3d 0%, #1a2840 100%)` - a dark gradient on a color gradient is not a photograph; proxybox.us, revoscape.com, and rootedmindsproject.org all put real photography behind their hero headlines; this pag
  4. 4. The display font is `Plus Jakarta Sans`, not Fraunces - the studio standard is Fraunces for headers OR a documented variation; this product's spec has no such documentation, making this a silent deviation.
  5. 5. `header p { color: #a0c4ff }` colors the hero sub-headline in a generic SaaS baby blue that appears in none of the declared brand tokens (`--wd-brand-primary: #0f1f3d`, `--wd-brand-accent: #1db87a`, `--wd-brand-surface: #eef2f7`) - remove i
  6. 6. The palette is navy/teal with zero warm tones - `#0f1f3d` + `#1db87a` + `#f8f9fa` is indistinguishable from 200 other AI FinTech starter kits; the studio standard is forest/gold/cream or a documented variation; this is neither.
  7. 7. Plus Jakarta Sans is fetched three separate times: in the `WD_SHELL_CSS_v1` block, directly in `<head>`, and again inside `WD_BRAND_OVERRIDE_v1` - redundant font requests that slow the page and indicate sloppy assembly.
  8. 8. The declared body font token is `--wd-brand-font-body: 'Inter'` but `body { font-family: 'Plus Jakarta Sans', sans-serif }` overrides it - the product's own brand token and its actual CSS contradict each other; pick one.
  9. 9. The meta description reads "Import transactions, categorize automatically, generate reports in seconds" - three sequential product verbs with no emotional hook; a 55-year-old freelancer who dreads tax time does not respond to feature lists,
  10. 10. The title says "Freelancers & SMBs," the meta body adds "consultants" as a third audience - three distinct buyers, none of them spoken to specifically; the hero cannot convert a freelancer and a 10-person agency with the same paragraph.
  11. 11. The schema tagline is "Your books, done by morning" - that is the strongest line on the page and it lives only in `<script type="application/ld+json">`; if that is not the visible H1 on the page, it is being wasted in metadata no visitor re
  12. 12. `.card h4 { color: #1db87a }` makes card headings the same green as the left accent bars and the `.cta-button` background - the single accent color appears simultaneously on borders, headings, and buttons, eliminating hierarchy; differentia
  13. 13. `.hero-image { max-width: 500px; margin: 40px auto }` - a centered 500px thumbnail is a postage-stamp treatment for what should be the product's money shot; either build a split-column layout with the image at full column width or use a ful
  14. 14. The tagline "Your books, done by morning" implies overnight automated processing as a literal product promise - if that is real, prove it with one sentence of mechanism; if it is marketing shorthand, it fails the honest copy standard.
  15. 15. The file system shows `about/`, `vs/`, `case-studies/`, `how-it-works/`, `faq/`, and `pricing/` all exist on disk - the WD shell nav links only to factory-wide pages (Catalog, How it works, Showcase, Pricing, Honest); the product needs its

carrier-onboarding-verification-voice-agent

Aug 29, 10:40 · 9KB · 15 demands shown
  1. 1. Fix `<meta name="description" content="">` - it is completely empty, meaning Google has nothing to display in search snippets and every share of this URL surfaces a blank description.
  2. 2. Complete the broken `<title>Carrier Onboarding Verification · </title>` - the brand name was never written after the separator dot, so every browser tab and search result reads as an unfinished sentence.
  3. 3. Fix the white-on-cream contrast failure in `.topbar`: `background:var(--ink)` resolves to `#f5f3f0` (cream) while `color:#fff` and `a{color:rgba(255,255,255,.85)}` render white text on that cream - the topbar is effectively invisible and fa
  4. 4. Fix the hero data card contrast failure: `.hero-card .row .r{color:var(--ink)}` renders cream text (`#f5f3f0`) on a white card background (`#fff`) - the "right column" values, which are the most important data in that card, are unreadable.
  5. 5. Fix the CSS syntax error `table.matrix .own{background:rgba(,.06)}` - the missing first rgba value silently breaks the "own" column highlight in every browser.
  6. 6. Apply Fraunces to every `h1` and `h2` - the hero heading inherits `font-family:var(--sans)` (Inter) despite Fraunces being loaded in the shell CSS, violating the studio's non-negotiable typography standard; compare proxybox.us where Fraunce
  7. 7. Put a real photograph in the hero - the above-fold layout contains only text, a stat grid, and a data card; per studio standards real photography is required in every hero, not optional, and no amount of dark-navy styling substitutes for it
  8. 8. Add `backdrop-filter:blur()` with a semi-transparent background to the sticky nav - `header.main` uses fully opaque `background:var(--bg)` with no blur, directly violating the studio's sticky tinted nav standard.
  9. 9. Document or revert the palette deviation - the page uses navy (`#1a2540`) plus orange (`#e8621c`) with no comment, commit note, or `deliberately-documented-variation` marker explaining why this departs from forest/gold/cream.
  10. 10. Source the hero stat pillars or remove them - the three large numbers in `.hero-pillars` have no attribution, methodology link, or footnote; per studio standards no big numbers without provenance.
  11. 11. Replace `.logo-mark` typographic fakes in the logos band with real SVG logos - if these represent actual carrier partners, show their real marks; if they are fabricated names, remove the band entirely rather than imply endorsements that do
  12. 12. Rewrite the product name as a buyer-benefit headline - "Carrier Onboarding Verification Voice Agent" is a spec-sheet label, not a headline; revoscape.com leads with the outcome the buyer gets, not the mechanism that delivers it; a 55-year-o
  13. 13. Add a pricing section - for a Tier 2 SMB tool, pricing transparency is a non-negotiable floor; the CSS contains no pricing class, and no visible nav link points to `/pricing` or a pricing anchor.
  14. 14. Add an FAQ section covering at minimum: how carrier data is sourced, what happens on verification failure, API vs. managed integration, and data retention - for a compliance tool, buyers block on exactly these questions and a missing FAQ se
  15. 15. Add a named social proof section - the CSS contains no `.testimonial`, `.review`, or `.quote` class; proxybox.us carries a named-client logo bar plus attributed quotes with titles and companies; this page has nothing, which is fatal for a p

afterhours

Aug 29, 10:01 · 9KB · 15 demands shown
  1. 1. The hero has no photograph. The entire hero section is a white background with text. Add a real photo of a service trade worker (HVAC tech, plumber, roofer) missing a late-night call. Every flagship reference site leads with real photograph
  2. 2. The h1 is the product name "AfterHours," not a value proposition. The actual headline is in the subheadline. Flip them: make "The night desk for service businesses" the h1 and reduce "AfterHours" to an eyebrow label above it.
  3. 3. The three stats (+35%, 82%, 3x) have no source, no methodology, and no attribution. Cite them parenthetically ("based on 30 beta accounts, Aug 2026") or remove them. Presenting fabricated-looking numbers on a page that is supposedly built o
  4. 4. The CTA button links to `#get-started` but that anchor does not exist in the page. The button goes nowhere. A page selling an after-hours lead capture product must itself capture leads. Wire it to a real form, a phone number, or a schedulin
  5. 5. The ICP is "service businesses," which could mean a law firm or a dog groomer. Name the exact buyer in every headline and feature card: HVAC technician, plumber, roofer, pest control operator. "Service businesses" is not a person.
  6. 6. There is no pricing on this page and no link to AfterHours-specific pricing. The nav goes to `/factory/pricing/` (Factory-wide). A Tier 2 SMB product must show what it costs or link to a dedicated pricing page. A plumber reading this page h
  7. 7. There is no FAQ section. Service business owners have obvious blockers: "What if the AI says something wrong?" "Which calendars does it support?" "What happens on a dropped call?" Tier 2 standard requires FAQ. None of these questions are an
  8. 8. Feature cards use the text character "checkmark" as their only visual treatment. Replace with real SVG icons (a phone, a calendar, a clipboard, a hand-off arrow). trydesk.org uses icon wrappers with background fills; proxybox.us uses real i
  9. 9. The page has four visible sections below the nav: "Why Night Leads Matter," "How AfterHours Works," "Results That Count," and one more partially visible. That is under the 6-section floor. Missing: a pricing section, an FAQ section, a testi
  10. 10. There are no testimonials of any kind, not even a single attributed quote from a beta user. revoscape.com has three named testimonials with photos and venue logos. This page has zero human validation for a product making specific performanc
  11. 11. The page says the agent "checks your calendar and books the first available slot" without naming which calendar systems are supported. An HVAC owner's first question is whether this works with Google Calendar, Jobber, or ServiceTitan. Name
  12. 12. The page has two `<header>` HTML elements. The shell nav uses `<header class="wd-shell-nav">` and then the hero content uses a second bare `<header>` tag. Change the hero wrapper to `<section id="main">` to fix the semantic duplication and
  13. 13. The page never says what AfterHours does not do. A service owner will assume it handles billing disputes, complaints, and dispatch. State the honest scope: "This is intake and scheduling only. Billing and complaints stay with your team." Ho
  14. 14. The body copy is well under 1200 words. The visible text totals roughly 400 words. A Tier 2 SMB landing page being actively sold needs 1200+ body words. Add a section walking through a real after-hours scenario, a section naming specific in
  15. 15. The comparison table compares AfterHours to unnamed alternatives. Name them. "vs. Ruby Receptionist," "vs. hiring a part-time answering service," "vs. leaving it to voicemail." A table with anonymous columns reads as made-up. Specificity ma

decision-maker-finder-ai

Aug 29, 09:47 · 11KB · 15 demands shown
  1. 1. The hero has zero photography - a centered `h2` on `#f8fafb` grey is not a hero, it is an error page; add a real photograph (sales pro at a desk, an org chart on a screen, anything with a human) the way vendoriq and investwithdreams anchor
  2. 2. The entire palette is `#2563eb` electric blue - CTAs, price numbers, and link states - replace with forest green primary (`#1f3a2e`), gold accent, and cream background; this page looks indistinguishable from a generic SaaS boilerplate.
  3. 3. The page background is `#f8fafb` (cold blue-grey) - change to cream (`#faf7f0` or equivalent); the studio palette is forest/gold/cream, not Github-issues grey.
  4. 4. The `.hero h2` has no `font-family` declaration and inherits Inter from body - Fraunces is loaded in the shell but never applied to the headline; add `font-family: 'Fraunces', Georgia, serif` explicitly to the hero heading.
  5. 5. The local `<style>` block sets `header { background: #fff; }` which is a bare-element selector that bleeds directly onto the WD_SHELL_NAV's `<header class="wd-shell-nav">` element and overrides its factory-defined tinted blur - scope every
  6. 6. The `.price` rule sets `color: #2563eb` - the studio standard explicitly forbids neon numbers on pricing displays; use dark ink or forest green.
  7. 7. The video banner promises "Watch the 30-second explainer" and links to the relative path `explainer.mp4` - no such file exists anywhere in the factory builds directory; fix the path or remove the banner, because a broken promise in the firs
  8. 8. The OG image is declared as `/factory/og/decision-maker-finder-ai.png` but no `/factory/og/` directory exists on the server - social shares for this product render with no image; create and deploy the OG card or remove the tag.
  9. 9. The feature cards are plain white boxes with grey borders and single-sentence descriptions - add at least one contextual photograph (a screenshot of the tool output, an annotated org chart, a real result) the way revoscape uses real environ
  10. 10. "Stop chasing org charts. Find who decides, fast." names no buyer - rewrite the hero headline to address the specific reader (e.g., an SDR who wastes Tuesday morning chasing a VP who doesn't own the budget), the way dailyunlock's hero speak
  11. 11. The JSON-LD `category` field is `"general saas"` - this is not a buyer-legible category; replace with a real market category (`"B2B Sales Intelligence"` or `"Prospecting Tool"`) and rewrite the `description` field from the current tag-line
  12. 12. The entry pricing tier is $5 - this floors perceived value and signals a toy; at Tier 2, the lowest paid tier should be no less than $29 or reframed as a credit-pack trial with a clear credit count and per-lookup price.
  13. 13. The page has zero social proof - no testimonials, no usage count, no company logos, no case study reference; at Tier 2, include at minimum two attributed quotes with first name, role type, and company size, or a single honest statistic with
  14. 14. No "How It Works" process walkthrough exists - add a numbered 3-step section showing the literal input/output (company name + target title → decision-maker name + verified contact) so a buyer can evaluate fit in under 20 seconds without rea
  15. 15. Section count is borderline - hero, features, comparison, pricing, FAQ, footer is the minimum floor, not a ceiling; add an ICP ("Who This Is For") section naming the three buyer types (SDR teams, founder-led sales, recruiting leads) with on

bookkeeper-ai

Aug 29, 09:40 · 10KB · 15 demands shown
  1. 1. The hero uses `linear-gradient(135deg, #0f1f3d 0%, #1a2840 100%)` with no photography. Replace with a real photo of a freelancer or small-business owner reviewing financials - the same move revoscape.com makes in every hero. Why: Real photo
  2. 2. Every heading is set in Plus Jakarta Sans. The page declares `--wd-brand-font-display: 'Plus Jakarta Sans'` and Fraunces is loaded in the shell but never assigned to any heading selector. Assign Fraunces to all `h1`-`h3`. Why: Studio standa
  3. 3. Every `.card` has `border-left: 4px solid #1db87a`. Remove all left accent bars unconditionally. Why: Explicitly banned by studio standards.
  4. 4. Every `.testimonial` also has `border-left: 4px solid #1db87a`. Same ban - and if these testimonials lack a real first name, last name, company, and role, delete them entirely. Why: Banned styling; no fake testimonials.
  5. 5. The palette is navy (#0f1f3d) and teal green (#1db87a) with a baby-blue hero sub-text (#a0c4ff). None of these are forest/gold/cream. Migrate to the studio palette. Why: Studio standard palette; the current colors read as a generic fintech
  6. 6. The hero H1 is the product name "Bookkeeper AI" - that is a logo, not a headline. Write a benefit-forward headline anchored in the prospect's pain. "Your books, done by morning" (already in the OG description) is stronger and should lead th
  7. 7. Google Fonts is loaded three separate times in the `<head>` (once in WD_SHELL_CSS_v1, once inline, once in WD_BRAND_OVERRIDE_v1). Deduplicate to a single `<link>` call. Why: Triple font loading adds latency and signals sloppy authorship to
  8. 8. The brand token system (`--wd-brand-primary`, `--wd-brand-accent`, etc.) is defined at the bottom of the `<head>` but the page CSS above it hardcodes hex values throughout - the tokens are installed and ignored. Either use the tokens or rem
  9. 9. The pricing schema declares a `lowPrice` of `$5`. A $5 bookkeeping tier is either a misleading teaser or a mislabeled free plan. The pricing section must name each tier clearly and explain exactly what $5 buys in plain language. Why: Honest
  10. 10. The meta description ("Import transactions, categorize automatically, generate reports in seconds") is a bullet-point list in prose disguise. Rewrite it as a prospect-aware sentence that names the buyer and the outcome. Why: This descriptio
  11. 11. The `.feature-item` CSS and `.features { background: #f8f9fa; }` reveal a feature section built from a list of text blocks. Add a real screenshot or in-context product photo to at least one feature block - proxybox.us puts real UI shots in
  12. 12. The CSS defines exactly five structural contexts: hero header, features section, pricing table, testimonials, footer. That is five sections - one below the required minimum of six. Add a named use-case or scenario section ("For freelancers,
  13. 13. The secondary CTA button (`.cta-secondary`) is defined as `background: transparent; border: 2px solid white; color: white`. On any non-dark background this button is invisible. Give it a legible appearance in both dark-hero and light-sectio
  14. 14. The hero sub-text uses `color: #a0c4ff` - a pale WCAG-failing blue on dark navy. Check the contrast ratio; it almost certainly fails AA at body-text size. Why: Accessibility floor; proxybox.us achieves strong contrast in its hero with delib
  15. 15. No FAQ section is evidenced anywhere in the CSS or schema. A bookkeeping AI product has obvious purchase-blocking questions: "Is my bank data secure?", "Does it file taxes?", "What accounting software does it sync with?" Add a real FAQ. Why

bookkeeper-ai

Aug 29, 08:58 · 11KB · 15 demands shown
  1. 1. The hero is a `linear-gradient(135deg, #0f1f3d 0%, #1a2840 100%)` with zero real photography. Replace it with an actual photo of a human at a desk, a bank statement on screen, or a receipt pile. Why: the standard is unambiguous -- real phot
  2. 2. The display font is Plus Jakarta Sans, not Fraunces. Either switch `h1`/`h2`/`h3` to Fraunces or write a one-line comment in the brand token block documenting why Plus Jakarta Sans was chosen. Undocumented overrides are invisible violations
  3. 3. The palette is `#0f1f3d` navy, `#1db87a` neon green, `#f8f9fa` gray. That is not forest/gold/cream. Pick forest/gold/cream or write down what palette this product uses and why it departs. Why: the studio standard requires either the house p
  4. 4. `.card { border-left: 4px solid #1db87a; }` -- remove every left accent bar on every card immediately. Why: the standard explicitly forbids left accent bars, full stop.
  5. 5. `.testimonial { border-left: 4px solid #1db87a; }` -- the testimonial pull-quotes also carry left accent bars. Remove them. Two forbidden elements for the price of one. Why: same rule, no left accent bars anywhere.
  6. 6. Every `.card` and the features section share background color `#f8f9fa`. Cards disappear into their own section background. Either give cards white fills with a real shadow or give the section a contrasting color. Why: look at how proxybox.
  7. 7. `header p { color: #a0c4ff; }` -- the hero subhead is rendered in cold blue, not cream. On a dark background, cream (#faf0e6 range) reads as editorial authority. Blue reads as a startup pitch deck. Why: the palette standard specifies cream
  8. 8. The `.pricing-table` is an HTML `<table>` with `border-collapse: collapse`. That is year-2010 pricing UX. Replace it with three side-by-side cards with a highlighted recommended tier. Why: every reference site at the solid tier and above us
  9. 9. The page has no real photography in any feature section. The `.features` section is flat gray with text cards. At minimum one section below the hero must contain a real photo of the product in use, a screenshot, or a person. Why: the standa
  10. 10. You are loading Plus Jakarta Sans twice: once inside the page `<head>` CSS block and again inside `WD_BRAND_OVERRIDE_v1`. Duplicate font loads cost real milliseconds on a page selling a productivity tool to people who already distrust slow
  11. 11. The bare `header { background: linear-gradient(135deg, ...) }` selector in the page `<style>` block will paint over the `.wd-shell-nav` factory header because the page CSS loads after factory.css and targets the same element. The shell nav
  12. 12. Count the sections: hero, features, pricing, testimonials, footer. That is four content sections and a footer. The floor is six sections. Add at minimum an FAQ section and a "who this is for" ICP section. Why: the studio standard explicitly
  13. 13. The `.testimonial` elements carry no names, no job titles, no company names, no photos. If these are anonymous pull-quotes you invented, delete them and say the product is new and has no testimonials yet. If they are real, add name, title,
  14. 14. The OG description is "Your books, done by morning." That is seven words. It tells a stranger nothing about who the tool is for, what it connects to, or why they should click. Rewrite to include the ICP ("freelancers who dread tax season")
  15. 15. The product lives at `wishdeal.com/factory/builds/bookkeeper-ai/` with factory chrome wrapping it. A freelancer getting this URL over text will immediately see "Wishdeal Factory" in the nav and read "this is a template showcase, not a real

sc-warm-signal-enrichment

Aug 29, 08:38 · 9KB · 15 demands shown
  1. 1. The hero has zero photography. Replace the `linear-gradient(135deg, #1a1f2e, #2d3a4a)` slab with a real image: a salesperson's screen showing a CRM record with a warm signal flagged, or a side-by-side of a cold list vs. an enriched one. Sto
  2. 2. The palette is navy (#1a1f2e) and orange (#e8541a). That is not forest/gold/cream, and it is not documented as a deliberate variation. Rebuild the color system to #1f3a2e, #c9a24a, and #faf7f0, or write a one-line documented reason why this
  3. 3. The proof-grid stats are orange numbers with labels and no source. Every figure needs a footnote: "based on N customers" or "internal benchmark, 90-day cohort." Unsourced big numbers fail the honesty standard.
  4. 4. The page has four sections: hero, features, proof, footer. The floor is six. Add a "How it works" process section (signal capture, enrichment, CRM push) and an "Who this is for" ICP section before claiming this page is shippable.
  5. 5. "Intent Detection for Sales Teams" is a category label, not a headline. Rewrite the h1 for the specific pain: your buyer is touring a competitor's site right now and your rep will find out in three weeks when it's too late.
  6. 6. The schema declares pricing at $5-$199 across three tiers but no pricing section exists on the page. Tier 2 requires pricing transparency on the page itself, not buried in JSON-LD that no prospect ever reads.
  7. 7. There is no FAQ section. Add five questions that handle the real objections for intent data: where the signals come from, how accurate the enrichment is, which CRMs it connects to, what happens to the data, and what a seat costs.
  8. 8. The product is titled "SC Warm Signal Enrichment" in the browser tab and OG title. "SC" is internal Sales Connector shorthand. A prospect who receives this URL by text will not know what "SC" means. Rename the public-facing title and h1 to
  9. 9. There is no named social proof anywhere. Revoscape carries three named photos with venue logos. This page needs at minimum one attributed quote with a first name, role, and company type. Anonymous stats do not substitute for a human voice.
  10. 10. Feature card body text is 14px at color #6b7280. That is WCAG-failing contrast on a white card at that size. Raise to 15px and #4a5568 minimum, or the accessibility pass fails before the copy quality even matters.
  11. 11. The hero CTA is styled but the linked text and destination are cut off in the provided HTML. If it lands on a generic unlock or checkout page, state the first specific action in the button: "Get your first 10 warm signals free" beats any ge
  12. 12. The copy visible in the first 8000 characters is thin enough that the full page almost certainly falls under 1200 body words. Count it. If it's under, write the difference before this page is sent to anyone.
  13. 13. There is no competitive positioning. Buyers evaluating intent data already know Apollo, Bombora, and 6sense. One sentence explaining what this does that those do not is the minimum price of entry for a category that crowded.
  14. 14. The background is `#f8f9fb`, a cool grey-blue. That reads as generic SaaS, not Wes's studio. The body background should be #faf7f0 or a warm near-white. This one CSS change removes the corporate-template feel immediately.
  15. 15. The footer is a single centered line with one orange link. It needs product links, a privacy policy, and a company link. The Slack-to-stranger test fails on any page with no legal footer and no way to navigate out.

iroh-p2p-video-collaboration

Aug 29, 08:16 · 10KB · 15 demands shown
  1. 1. The hero uses `linear-gradient(135deg, #fafaf9 0%, #f5f0ed 100%)` with no `img` tag anywhere - pull a real photograph (developers at laptops, a network diagram over a real workspace, anything physical) exactly as vendoriq.html does with its
  2. 2. `.code-block { border-left: 4px solid #1a1a1a }` is a left accent bar, which is explicitly banned by studio standards - replace it with a language-labeled header tab or a fully-bordered terminal card with a `#1f3a2e` top stripe.
  3. 3. The entire palette is undocumented monochrome (`#1a1a1a`, `#fafaf9`, `#4a4a45`, `#e5e5e0`) with no Forest green, no gold, no cream accent - either adopt the studio palette or write a one-sentence justification in the build notes; right now
  4. 4. The `<title>` tag claims "Zero-Latency Data Sync" - P2P over NAT traversal is provably higher latency than centralized CDN under most real-world conditions, so remove or replace this with a defensible claim like "low-overhead" or "no relay
  5. 5. The OG title is `iroh-p2p-video-collaboration · Wishdeal Factory` while the page `<title>` is `Iroh P2P Sync | Build Collaborative Apps` - these name two different products; pick one name and use it in every meta, heading, and JSON-LD field
  6. 6. The JSON-LD sets `"category": "content"` for what is clearly a developer SDK - change the schema type to `SoftwareApplication` and the category to `"Developer Tools"` so rich snippets fire correctly in search.
  7. 7. The page CSS defines its own `nav { display: flex; border-bottom: 1px solid #e5e5e0 }` block inside the inline `<style>` tag, which conflicts with WD_SHELL_NAV_v1 already injected by the Factory shell - remove the redundant nav styles entir
  8. 8. The `.cta-button { background: #1a1a1a }` is a plain black rectangle with no brand identity - replace with `#1f3a2e` (Forest) or the documented brand accent so the CTA doesn't read as a generic Bootstrap default.
  9. 9. The feature grid is two text columns with a `border-bottom` divider and nothing else - add at least one photographic element per feature cluster the way proxybox.us anchors each capability to a real device or interface screenshot.
  10. 10. There is no visible pricing section in the page HTML despite the JSON-LD declaring a $5-$199 offer range - a product with three price tiers needs a named pricing section on the page, not structured data buried in the `<head>`.
  11. 11. "Iroh" is never introduced - the first 8000 characters never state who built it, what language it is written in, or what it replaces - a developer landing page must answer "what is this actually" in the opening two paragraphs before selling
  12. 12. The page never resolves whether it is selling a Wishdeal Factory bundle of Iroh or the Iroh open-source library itself - a developer who lands here cannot tell if they are buying integration work, a hosted service, or a documentation bundle
  13. 13. There are no social proof elements of any kind - no GitHub star count, no named project that ships with Iroh, no developer quote with a real name and company - compare revoscape.com which names specific venue clients; even a single attribut
  14. 14. The URL slug is `iroh-p2p-video-collaboration` but the meta description says "offline-ready collaborative applications" and the body copy title says "Iroh P2P Sync" - commit to one use case in the slug, the headline, and the description, be
  15. 15. The CSS shows only `.hero`, `.section`, `.section.alt`, and `.footer` - that is three content zones at most, well below the six-section floor - add Problem, How It Works, Use Cases, and Pricing as named sections before calling this page com

bookkeeper-ai

Aug 29, 07:21 · 10KB · 15 demands shown
  1. 1. The inline `<style>` block overrides `body { font-family: 'Plus Jakarta Sans', sans-serif }`, displacing the shell's mandated Inter - strip this override entirely; the shell already loads Inter and there is no documented variation on file.
  2. 2. The page loads Plus Jakarta Sans as a fourth font family alongside Fraunces, Inter, and JetBrains Mono already pulled by the shell - remove it; this wastes ~15KB of font payload for a font the page then uses exclusively in place of the corr
  3. 3. Both `.card` and `.testimonial` share `border-left: 4px solid #1db87a` - two distinct element types, identical left accent bars, which is explicitly prohibited; remove the accent bar from both and differentiate cards by background or shadow
  4. 4. The hero is a CSS gradient (`linear-gradient(135deg, #0f1f3d, #1a2840)`) with no `<img>` - this page requires real photography in the hero; put a photograph of a freelancer or small-business owner reviewing a clean financial report behind o
  5. 5. Feature grid `.card` elements appear to contain only a headline and text, with no photography - add at least one real image to the primary feature block; investwithdreams and revoscape both use real imagery inside feature rows, not icon-fre
  6. 6. The palette is navy (#0f1f3d) + bright green (#1db87a) + electric blue (#a0c4ff) - none of these are forest/gold/cream, and there is no documented variation; align to the standard palette or formally document a deliberate deviation before t
  7. 7. Hero subtext is styled `color: #a0c4ff` - a bright blue that reads neon in a dark hero; replace with warm cream (#faf7f0) or soft warm gray.
  8. 8. Testimonials are marked up with only a left accent bar and no visible name, title, or photo in the CSS structure - every testimonial must carry a real full name, role, and photo or be removed; revoscape shows three named individuals with ve
  9. 9. The CSS defines hero + features + pricing + testimonials + footer - that is likely five sections, one below the six-section floor; add a concrete "Who it's for" ICP block naming freelancers vs. consultants vs. side-hustle operators as disti
  10. 10. All page CSS lives in an inline `<style>` block that fights factory.css for specificity - this is unmaintainable and creates silent rendering bugs when the shell updates; move overrides into a linked per-build stylesheet or extend factory.c
  11. 11. The hero has no social proof anchor - proxybox.us puts a real usage number or trust line directly beneath its hero CTAs; add one honest line ("Categorized [N] transactions this month" or a named beta-user quote) or nothing at all; do not in
  12. 12. The pricing section uses a flat HTML `<table>` with `border-collapse: collapse` - a table is not a pricing section; replace with three tier cards (free / professional / business) with a visually highlighted recommended plan, as spearplus.co
  13. 13. The meta description reads "Import transactions, categorize automatically, generate reports in seconds" - this is a feature dump, not a positioning statement; rewrite to name a specific buyer pain: "Freelancers lose hours every month reconc
  14. 14. The body has two `<header>` landmark elements (the shell nav `<header class="wd-shell-nav">` and the hero `<header>`) - invalid HTML semantics; change the hero section to `<section class="bk-hero">` or `<div class="hero">`.
  15. 15. The JSON-LD includes an Adoptability Score of 82 - if this number renders visibly on the page without a direct link to the /factory/honest/ methodology page, it is a big number without provenance; every displayed score must be hyperlinked t

bookkeeper-ai

Aug 29, 06:53 · 11KB · 15 demands shown
  1. 1. The body font is `Plus Jakarta Sans` declared inline, overriding the shell's Fraunces/Inter load - strip that style block entirely and use the shell typography that every other Factory build uses. Why: the standard is non-negotiable Fraunce
  2. 2. The hero is a CSS gradient (`linear-gradient(135deg, #0f1f3d, #1a2840)`) with no photography - replace it with a real image of a person at a desk reviewing financials, the same way revoscape leads every section with venue photography. Why:
  3. 3. Every feature card carries `border-left: 4px solid #1db87a` - remove left accent bars from all cards unconditionally. Why: left accent bars are explicitly prohibited; spearplus and proxybox both use shadow + background contrast to different
  4. 4. The testimonial block also uses `border-left: 4px solid #1db87a` - same violation, same fix, and while you're there, add a real full name, job title, and business name to each testimonial or remove the section. Why: anonymous testimonials a
  5. 5. The palette is navy (#0f1f3d) and bright green (#1db87a) throughout - neither maps to forest/gold/cream; audit every hex value on the page and migrate to the documented palette or file a deliberate variation note. Why: no rainbow palettes i
  6. 6. Feature section block imagery is absent entirely - the `.grid .card` elements appear to contain only text; add a real contextual photo or illustrated screenshot to each of the top three feature cards. Why: real photography in section featur
  7. 7. Count the distinct sections: hero, features, pricing table, testimonials, footer is five at most - add at least one more substantive section (a how-it-works walkthrough, an integration list, or a use-case scenarios block) to reach the six-s
  8. 8. The hero subtitle reads `color: #a0c4ff` (light blue) and says something generic - that color is not in the palette and the line reads like a feature bullet, not a hook that speaks to the specific pain of a freelancer doing books at midnigh
  9. 9. The `header p { color: #a0c4ff; }` neon blue does not belong to any documented palette and will read as washed-out lavender on mobile - replace with a warm cream or off-white that sits inside the forest/gold/cream system. Why: no neon hero
  10. 10. There are no sub-pages scoped to Bookkeeper AI - no `/bookkeeper-ai/pricing/`, no `/bookkeeper-ai/faq/`, no `/bookkeeper-ai/about/` - add at minimum a standalone pricing page and an FAQ page with internal links from the main build page. Why
  11. 11. The `.pricing-table` is a raw HTML table with no plan names or feature comparison visible in the markup - verify that the rendered table includes named tiers, dollar amounts with billing cadence, and a clear differentiator column; a table o
  12. 12. The `footer` is a single centered line on `#0f1f3d` with no product links, no legal links, no email, and no secondary CTA - add at minimum a product link column and a contact or support email. Why: capitolcellars and proxybox both treat the
  13. 13. The page's `<title>` uses a hyphen as separator ("Bookkeeper AI - Accounting Automation") while every other Factory build uses a middot - fix to match the shell convention and make the title unique enough that it doesn't read like a commodi
  14. 14. The `.card h4 { color: #1db87a }` reinforces the wrong green throughout the feature grid - change card heading color to the forest dark or a gold accent from the correct palette. Why: palette discipline is not decorative; vendoriq maintains
  15. 15. The page body is almost certainly under 1,200 words given the minimal card and table structure visible - audit the rendered word count and expand the copy to meet the floor, focusing on the specific failure modes (missed deductions, tax-tim

solo-analytics

Aug 29, 05:26 · 10KB · 15 demands shown
  1. 1. The hero font is `Plus Jakarta Sans`, not Fraunces. The shell CSS loads Fraunces and the page overrides it with an undocumented Google Fonts sans-serif. Replace every `font-family: 'Plus Jakarta Sans'` declaration with `Fraunces` for displa
  2. 2. The hero background is `linear-gradient(135deg, #111827 0%, #1a2340 100%)` with no `<img>` anywhere in the hero block. Every flagship reference (proxybox, revoscape, investwithdreams) uses real photography as the hero anchor. A CSS gradient
  3. 3. The palette is Tailwind neon green `#22C55E` on dark navy `#111827` on slate `#F1F5F9`. The studio palette is forest/gold/cream. No flagship uses this color set. Rebuild the palette or document the deviation with a named reason in the build
  4. 4. `.testimonial { border-left: 4px solid #22C55E; }` is an explicit studio ban. Remove the left accent bar from every testimonial card.
  5. 5. All three testimonial cards carry the identical `border-left: 4px solid #22C55E`. That is the "identical gradient borders on cards" antipattern. If testimonials need a visual treatment, use varied photography avatars as revoscape does.
  6. 6. `.pricing .price { font-size: 48px; color: #22C55E; }` is a neon hero number. Banned. Render the price in forest `#1f3a2e` or ink `#111827`.
  7. 7. `.feature h3 { color: #22C55E; }` puts neon green on every feature title. This is not a brand accent, it is the entire Tailwind green-500 swatch. Replace with forest or a muted gold so features read as studio work, not a Next.js starter.
  8. 8. `body { background: #F1F5F9; }` is Tailwind slate-100, not cream `#faf7f0`. Every studio flagship (dailyunlock, proxybox, rootedmindsproject) uses cream as the body canvas. Fix this before the palette issue even registers as intentional.
  9. 9. The feature section has `padding: 0` cards with zero imagery. Vendoriq and proxybox both pair each feature block with a supporting visual (screenshot, icon set with real context, or photo). Feature text alone is a spec sheet, not a page.
  10. 10. The page defines `header { background: #111827; padding: 24px 0; }` alongside the shell nav injection. If both mount, the user sees two nav bars. If the page header is a second element below the shell, delete it and its CSS entirely.
  11. 11. The page-level header has no `position: fixed` and no `backdrop-filter`. If the shell nav is handling sticky behavior, the page header CSS is dead weight that conflicts. If the shell nav is NOT handling it, the page has a static header that
  12. 12. The page loads a second `<link>` to Google Fonts for Plus Jakarta Sans independent of the shell CSS. The shell already loads Fraunces and Inter. Fix the font to Fraunces and drop the redundant font request, which adds ~200ms on mobile.
  13. 13. There is no product screenshot, dashboard preview, or screen capture anywhere in the hero or feature sections. An analytics product must show the analytics UI. Voicetrail shows its recorder interface in the hero. Solo Analytics shows nothin
  14. 14. The testimonials have no photo avatars and likely carry non-verifiable attribution (the CSS has `testimonial-author` and `testimonial-role` fields but no `<img>`). A named author without a face and a domain is functionally anonymous. Either
  15. 15. The comparison block uses `font-size: 14px; opacity: 0.9` inside a `#111827` dark container. If this block compares Solo Analytics to GA4 or Mixpanel, that argument needs to be legible and structurally prominent, not a footnote. Rebuild it

bookkeeper-ai

Aug 29, 05:03 · 10KB · 15 demands shown
  1. 1. Replace `Plus Jakarta Sans` with `Fraunces` on every `h1`, `h2`, `h3`, and `.logo` - the studio non-negotiable is Fraunces serif headers + Inter body, and this page ignores it entirely.
  2. 2. Swap the navy/mint palette (`#0f1f3d` / `#1db87a`) for forest/gold/cream - the current scheme reads as a generic fintech SaaS, not a Wishdeal Factory product, and breaks palette coherence across the network.
  3. 3. Add `position: sticky; top: 0; backdrop-filter: blur(12px);` to the header - the nav is fully static and disappears on scroll, violating the sticky tinted nav standard that every flagship site including proxybox.us enforces.
  4. 4. Fix mobile navigation: `nav { display: none; }` at 768px removes all navigation with zero replacement - every mobile visitor is stranded with no way to reach pricing, FAQ, or any sub-page.
  5. 5. Put real photography in the hero - a dark gradient with text is not a hero, it is a placeholder; opm-group.biz, revoscape.com, and rootedmindsproject.org all lead with a concrete visual that grounds what the product does.
  6. 6. Put at least one real photo in the feature section - white text cards with colored circle "badge icons" are not feature blocks, they are bulleted lists with extra steps.
  7. 7. Remove the colored circle `badge-icon` div masquerading as a trust signal - a div with `background: #1db87a` and a font-weight: 700 checkmark is not a trust badge; cite something verifiable (SOC 2 pending, QuickBooks integration, IRS-compli
  8. 8. `Plus Jakarta Sans` is loaded twice and `Inter` is loaded twice in `<head>` - deduplicate; the factory shell already loads Inter, and a second Google Fonts call for the same weight set adds latency for nothing.
  9. 9. There is no named social proof anywhere in the visible HTML - a bookkeeping product that touches real business finances needs at minimum one named person, their business type, and a specific outcome, not anonymous trust badge theater.
  10. 10. Rewrite the hero headline: "Autonomous Accounting for SMBs" is a category label, not a promise - write for the actual buyer: the 10-person shop owner who is manually reconciling bank statements at 11 PM.
  11. 11. Audit body word count against the 1200-word floor - factory-generated pages routinely run 400-600 words; expand with concrete workflow scenarios, not marketing abstractions.
  12. 12. The nav is not visible in the HTML excerpt - confirm that sub-pages exist and are linked (pricing, FAQ, about, security), not just `#anchor` links scrolling to sections on one page.
  13. 13. The `$5` `lowPrice` in the JSON-LD implies a $5 tier exists on the pricing section - if it does, that tier's limitations must be stated honestly on the page before the user clicks; pricing pages that hide what the cheap tier cannot do train
  14. 14. The footer is a single centered text block - spearplus.com, proxybox.us, and revoscape.com all have footers with real nav columns, legal links, and a secondary CTA; this footer provides no recovery path for a visitor who scrolled past prici
  15. 15. The hero CTA group has two buttons ("Get Started" / "See How It Works" presumably) but neither CTA tells the user what happens next - "Start Free Trial," "Book a Demo," or "Connect Your QuickBooks" are specific; generic button labels indica

law-firm-ai

Aug 29, 03:42 · 10KB · 15 demands shown
  1. 1. Replace the dark-navy palette (`#0f172a` / `#3b82f6`) with forest/gold/cream or document explicitly why a law-firm product gets a blue tech startup palette. Why: every reference flagship uses a deliberate, documented palette variation, not
  2. 2. The `h1` and `h2` inherit `font-family:'Inter'` from the body rule -- Fraunces is loaded but never applied to any header selector. Why: the studio standard is Fraunces for headers, and omitting it is not a documented variation.
  3. 3. There is no real photography anywhere on this page. Add at least one hero photograph -- a lawyer reviewing a document, a deposition transcript on a desk, anything real. Why: proxybox.us uses a real device photo in the hero; revoscape.com us
  4. 4. The page is a single narrow column (`max-width:780px`) with a link list and an audio player. Build at least 6 distinct sections: hero, problem, how it works, use cases, pricing, FAQ. Why: the studio floor is 6+ sections and this page has on
  5. 5. The meta description reads "Law Firm AI is being finished. Audio pitch and explainer video are available now." That copy is live on a public URL. Rewrite it to the actual value proposition. Why: revoscape.com and proxybox.us both ship meta
  6. 6. The `<title>` is "Law Firm AI." That is not a title, it is a category label. Rewrite it: something like "Law Firm AI -- Document Review and Case Research for Solo and Small Firm Attorneys." Why: investwithdreams.com and revoscape.com both u
  7. 7. The structured data shows `lowPrice: 5` and `highPrice: 199` but the page body has no visible pricing section. Either add a pricing section or remove the schema until the page is ready to sell. Why: honesty standard -- pricing in the JSON-L
  8. 8. The primary CTA visible on this build is "Commission a build" in the shell nav, which points to the factory operator-partnership page, not this product's unlock. Add a product-specific primary CTA button on the body. Why: every flagship pag
  9. 9. The product has no body copy explaining who this is for. A solo practitioner, a legal ops director at a 50-attorney firm, and a paralegal have completely different jobs. Name the ICP in the first three sentences. Why: revoscape.com's hero c
  10. 10. The audio pitch and explainer video are embedded raw with no surrounding copy -- no title, no runtime, no one-sentence summary of what the listener will hear. Wrap them with enough context that a stranger knows whether to spend 4 minutes li
  11. 11. There are zero testimonials, named clients, or case-study references anywhere in the visible HTML. For a Tier 2 SMB tool, add at least two named social proof elements (even from a beta user or pilot firm). Why: revoscape.com shows named ven
  12. 12. The body word count on this page is almost certainly under 200 words. The studio minimum for a page being sold is 1200+ body words. Write the copy. Why: thin pages signal thin products.
  13. 13. The `ul.links` navigation list is the primary content delivery mechanism. Links to what -- the pitch, the explainer, the unlock page? Each link label needs a descriptor of what the user will find, not just an arrow. Why: proxybox.us and ven
  14. 14. The page has no FAQ section. For a law firm audience (who will ask about privilege, data storage, malpractice exposure), FAQ is not optional. Add a minimum of 6 real questions with honest answers. Why: the studio Tier 2 standard explicitly
  15. 15. The `h2` elements use `font-size:1.25rem` with no weight specification and no Fraunces. Every section header should use Fraunces at a weight that creates visual hierarchy distinguishable from body text. Why: spearplus.com and investwithdrea

bookkeeper-ai

Aug 29, 03:37 · 11KB · 15 demands shown
  1. 1. Replace Plus Jakarta Sans on every heading with Fraunces -- the factory shell CSS loads Fraunces then the page's own `<style>` block clobbers it with Plus Jakarta Sans on h1, h2, h3, .logo, .price, and .faq summary. Why: documented studio s
  2. 2. Burn the navy/green palette (#0f1f3d, #1db87a) and rebuild in forest/gold/cream -- the current palette is indistinguishable from 40,000 other B2B SaaS templates and shares nothing with the studio's identity system. Why: studio standard, pal
  3. 3. Put a real photograph in the hero -- a small business owner at a desk with a laptop or a tidy office backdrop, not `linear-gradient(135deg, #0f1f3d 0%, #1a2d4a 100%)`. Why: every reference flagship from revoscape to vendoriq uses hero photo
  4. 4. Fix the mobile breakpoint -- `@media (max-width: 768px) { nav { display: none; } }` removes the entire nav with zero hamburger replacement, leaving mobile visitors with no way to reach any page. Why: basic navigation is not optional.
  5. 5. Make the header sticky with `position: fixed` and `backdrop-filter: blur(16px)` -- the current header is static and vanishes on scroll; every reference site has a tinted sticky nav. Why: studio standard, explicitly named.
  6. 6. Add real photography to at least two feature blocks -- `.feature-block` cards are white boxes with a headline and a gray paragraph and nothing else; photography in feature blocks is a listed studio standard, not decoration. Why: studio stan
  7. 7. Add a minimum of two more named sections to hit the 6-section floor -- the visible structure is hero, one features grid, pricing, FAQ, footer -- that is five, one short of the minimum, with no social proof or process/how-it-works section. W
  8. 8. Rewrite the hero headline out of investor-pitch language -- "Autonomous Accounting for SMBs" is what you say in a deck; the buyer says "I spend three hours every Sunday fixing my books." Speak to the pain, not the product category. Why: stu
  9. 9. Explain each pricing tier in three bullet points or a feature list -- the price cards show dollar amounts and labels but $5/month for "autonomous accounting" with no scope description reads as an unfilled placeholder. Why: Tier 2 SMB tools
  10. 10. Remove `transform: scale(1.05)` from the featured price card -- this is a 2019 SaaS template trick that the reference sites abandoned; it looks cheap and reads as clip art. Why: studio standard rejects identical gradient borders and identic
  11. 11. Replace the CSS-circle trust badges (the green dot + a checkmark character) with claims that have a source -- a specific encryption standard, a named accounting certification, or a money-back guarantee with terms. Why: studio standard, hone
  12. 12. Show integration logos (QuickBooks, Xero, Stripe, Plaid, at least one bank connection) with real marks above the fold or in its own section -- an accounting product that does not show how it connects to your existing bank and software will
  13. 13. Add a scroll-reveal animation pass -- every reference site from dailyunlock to proxybox to investwithdreams uses opacity + translateY reveals; this page renders flat and static, which signals template rather than crafted product. Why: craft
  14. 14. Fix the double space in the title tag -- `Bookkeeper AI - Autonomous Accounting for SMBs` has two spaces before and after the dash; fix to a single space or use a proper separator. Why: this character error appears in every browser tab an
  15. 15. Replace the JSON-LD description `"Your books, done by morning."` with a substantive 1-2 sentence product description -- a tagline is not a schema description, and search crawlers use this field for rich snippet text. Why: basic SEO hygiene;

decision-maker-finder-ai

Aug 29, 03:26 · 10KB · 15 demands shown
  1. 1. The page-level `<style>` block hardcodes `color:#2563eb` for all accents and CTAs, overriding factory.css with a generic SaaS-blue palette that shares nothing with the forest/gold/cream brand standard shown in the factory nav's own `#1f3a2e
  2. 2. The hero `h2` style block sets `font-weight:700` but no `font-family`, meaning the headline renders in Inter (inherited from body), not Fraunces. Every flagship build from proxybox to dailyunlock leads with a Fraunces serif headline. This o
  3. 3. No real photography exists anywhere on the page: not in the hero, not behind feature cards, not in any section. proxybox.us puts a real device photo in the hero; revoscape's every section block uses real job-site photography. This page has
  4. 4. The sticky nav uses `background:#fff` with a hard `border-bottom:1px solid #e2e8f0`. Add `backdrop-filter:blur(12px)` and a semi-transparent forest tint. Every flagship in the corpus uses this pattern; this page is the only one with an opaq
  5. 5. The video banner at the top links `explainer.mp4` as a bare relative URL with no guarantee the file exists at that path. Either embed the video inline in the hero (below the headline) or remove the banner entirely. A broken or empty video l
  6. 6. The body background is `#f8fafb`, a cool blue-gray that signals "generic startup" rather than Wishdeal Factory. Replace with warm cream (`#faf7f0` or equivalent) consistent with the favicon, the nav bar, and every other Factory build.
  7. 7. The feature card paragraphs render at 14px in `#64748b`, a color that fails WCAG AA contrast on the `#fff` card background. Raise body copy to 15px minimum, darken to `#4b5563` or deeper.
  8. 8. The comparison table lists anonymous alternatives. Name the actual competitors: Apollo, ZoomInfo, LinkedIn Sales Navigator. revoscape's comparison section names the specific incumbents (property management software) by category so readers c
  9. 9. There is no "How it works" process section. The page moves directly from feature cards to a pricing table without ever explaining the mechanism: what does a user input, what does the tool return, how long does it take. voicetrail.ai shows a
  10. 10. The pricing section shows `$5` to `$199` with no framing of what those numbers unlock relative to the problem's cost. The page never says "Apollo charges $X per seat." spearplus anchors every price against the outcome it delivers; this pric
  11. 11. There is no named social proof with a face anywhere on the page. Not a quote, not a logo bar, not a named company. revoscape shows named property managers with venue logos. At Tier 2, at minimum two real named quotes (company and title, no
  12. 12. The hero sub-paragraph is capped at `max-width:600px` and addresses no specific buyer persona. Who is this for: an SDR at a 20-person SaaS company? A fractional sales person at an agency? dailyunlock.us names its reader in the second senten
  13. 13. The FAQ answers are `display:none` with no server-rendered fallback and no `<noscript>` alternative. Every answer is invisible to search crawlers and screen readers, destroying the SEO value of the one content type on the page that naturall
  14. 14. The `<footer>` is a single centered `#0f1117` bar with no navigation, no product links, no legal footer, and no trust signals. proxybox.us has a four-column footer with product sub-pages, legal links, and a copyright line. This footer is a
  15. 15. There are no inline CTAs between the hero and the pricing section. After the hero button, nothing is clickable for four full sections (features, comparison, how-it-works-that-doesn't-exist, social-proof-that-doesn't-exist). Add a CTA at min

bookkeeper-ai

Aug 29, 02:58 · 10KB · 15 demands shown
  1. 1. Replace Plus Jakarta Sans on every heading with Fraunces. The shell CSS already loads Fraunces; the page overrides it with an undocumented sans-serif stack on h1, h2, h3, and the logo. This is a studio standard violation, not a stylistic ch
  2. 2. Put a real photograph in the hero. `linear-gradient(135deg, #0f1f3d 0%, #1a2d4a 100%)` is a gradient, not a hero image. Vendoriq's hero has a full-bleed office photo behind the headline. A bookkeeping product aimed at SMBs should show a rea
  3. 3. Kill the navy/mint palette and document a deliberate replacement. `#0f1f3d` and `#1db87a` are not forest/gold/cream and no rationale is written anywhere. Pick a palette and defend it in writing, or conform to the standard.
  4. 4. Make the nav sticky with `position: sticky; backdrop-filter: blur(12px)`. The current `header` is static and opaque. Every flagship site in the reference set uses a sticky frosted nav. This one scrolls away.
  5. 5. On mobile, `nav { display: none }` with no hamburger replacement means mobile users have no navigation at all. Vendoriq and TryDesk both have working mobile navs. Fix it.
  6. 6. Add real photography to the feature blocks. The `.feature-block` cards are white boxes with a title and a paragraph. The standard demands real photography in section feature blocks, not text-only cards with a thin `#eef0f4` border.
  7. 7. You have 5 sections: hero, features, pricing, FAQ, footer. Six is the floor. Add a "How it works" step section, a "Who it's for" ICP section, or a comparison block. One of these is missing and it shows.
  8. 8. Replace the fake green-circle trust badges with real ones. `<div class="badge-icon">✓</div>` next to "Bank-grade security" is a painted checkmark, not a trust signal. Show a real bank logo, a real integration badge, or a real certification
  9. 9. The headline "Your books, done by morning" does not say who this is for, what it replaces, or what "done" means. A 55-year-old plumber reading this cannot tell if this is for them. Rewrite to name the buyer and the job: "Bookkeeping for tra
  10. 10. "Autonomous Accounting" in the title tag is a liability, not a feature. Name what the AI actually does: categorizes transactions, reconciles bank feeds, closes the month. Do not use "autonomous" without constraint. Every SMB owner who has b
  11. 11. The pricing `lowPrice: "5"` in the JSON-LD is not explained on the page. If $5 buys something real, say what. If it is a freemium hook, label it "Free starter." Unexplained low anchor prices read as bait-and-switch, not generosity.
  12. 12. The price cards use `transform: scale(1.05)` and `border-color: #1db87a` as the only differentiation for the featured tier. Look at how investwithdreams.com separates its featured plan with a background fill, a badge, and a contrasting CTA.
  13. 13. Plus Jakarta Sans is loaded twice (once inside the WD_SHELL_CSS_v1 block, once again in the page `<head>`) and Inter is also loaded twice. This is a performance and maintenance debt that signals the page was assembled by copy-paste without
  14. 14. The nav on desktop shows no sub-page links to /pricing, /faq, /about, /security, or /integrations. Even if those pages are stubs, the standard requires real internal links. A prospect clicking around and finding dead nav items will not conv
  15. 15. There is no comparison content. At Tier 2, a single "Bookkeeper AI vs. a traditional bookkeeper" table is enough. The page currently makes no argument for why this beats the incumbent. ProxyBox has a comparison section. This page does not.

white-label-document-collection-portal-for-law-fir

Aug 29, 02:43 · 12KB · 15 demands shown
  1. 1. The hero is a pure CSS gradient with zero photography. Replace it with a real photograph of a law firm professional receiving a completed document set, or a genuine UI screenshot of the branded portal itself. Why: studio standard requires r
  2. 2. The font stack is Libre Baskerville + Source Sans 3. This is not Fraunces + Inter and no variation is documented anywhere. Swap to Fraunces + Inter or file a written variation justification. Why: undocumented font departures are not permitt
  3. 3. The palette is `#1c2b3a` slate + `#a3321d` rust + `#eef1f4` cold blue-grey. This is not forest/gold/cream and no variation is documented. Why: same rule as fonts -- palette departures require explicit documentation.
  4. 4. The Problem card and the Solution card both carry `border-left: 4px solid` accent bars. Left accent bars are explicitly prohibited. Remove them and differentiate the two panels through background, typography weight, or photography. Why: stu
  5. 5. Every FAQ item has `border-left: 4px solid #a3321d`. This is four or more additional prohibited left accent bars. Strip all of them and style the FAQ with open/close chevrons or a clean rule between items. Why: same prohibition as above, co
  6. 6. Feature icons are bold single letters in colored squares (`background: #a3321d; font-weight: bold`). This is a stock SVG icon substitute in spirit. Replace with real product UI screenshots cropped to each feature, or genuine photography. Wh
  7. 7. The "How It Works" three-step grid uses numbered circles with prose only. A law firm buyer needs to see the actual portal screen they are buying. Add a real UI mockup or annotated screenshot under each step. Why: revoscape.com shows the act
  8. 8. Rust red `#a3321d` is applied to buttons, h3 headings, step circles, feature icon backgrounds, FAQ bars, and card borders simultaneously. A 55-year-old law firm managing partner associates this color with consumer apps and error states, not
  9. 9. The `#eef1f4` body background reads as a hospital intake form. A premium white-label portal for law firms demands a warmer off-white or a deliberate dark-mode treatment. Why: capitolcellars.com achieves immediate visual authority through de
  10. 10. The security section is a three-column text grid on a dark band with no icons, no certification badges, no visual hierarchy inside the band. Law firm buyers evaluating a document portal will scrutinize security more than any other section.
  11. 11. There is zero social proof on the entire page. No named attorney, no firm name, no quote, no logo. A Tier 2 SMB tool selling to law firms needs at minimum one named testimonial from a real attorney with their role and firm type visible. Why
  12. 12. The hero headline and tagline ("Every document. Collected. On time.") speak in operational language but do not name the buyer's pain. A law firm partner's pain is missed closings, late client intake, malpractice exposure from incomplete fil
  13. 13. The generic CTA "Get a Free Demo" is used in both the hero and the footer with no differentiation. The hero CTA should name the specific outcome ("See your firm's branded portal in 10 minutes") while the footer CTA should address the late-f
  14. 14. No sticky navigation with `backdrop-filter: blur` is present in the page HTML. The shell CSS loads from `factory.css` but no `<header>` or `<nav>` element appears in the document body. If the factory shell injects a nav, verify it meets the
  15. 15. The pricing section has three tiers but the feature differentiation between them is not visible in the first 8000 characters. Law firm buyers comparing tiers need to see exactly what changes between $5, the middle tier, and $199 -- list lim

bookkeeper-ai

Aug 29, 02:34 · 10KB · 15 demands shown
  1. 1. Replace `Plus Jakarta Sans` with Fraunces on every heading (h1, h2, h3, .logo, .faq-item summary). Why: The WD shell loads Fraunces explicitly; this page overrides it in a custom style block, breaking cross-portfolio brand coherence that ev
  2. 2. Make the header sticky: `position: sticky; top: 0; backdrop-filter: blur(12px); background: rgba(15,31,61,0.85)`. Why: Studio standard is non-negotiable; proxybox.us, revoscape.com, and thespear-ai.com all use sticky tinted nav, and this he
  3. 3. Replace the hero's `linear-gradient(135deg, #0f1f3d 0%, #1a2d4a 100%)` with a real photograph, a small-business owner reviewing financials at a desk or laptop. Why: Studio standard demands real photography in every hero; a near-identical na
  4. 4. Add a real photograph inside at least two of the feature section blocks, either a UI screenshot or a contextual image. Why: Studio standard; text-only white cards with no visuals are the feature section equivalent of stock SVG icons, which
  5. 5. Rewrite "Autonomous Accounting for SMBs" to a headline a 55-year-old plumber understands without googling either word. Why: "Autonomous" and "SMBs" are VC deck vocabulary; proxybox.us says "Own Your Internet" because the buyer knows what ow
  6. 6. Kill the mobile `nav { display: none; }` and replace it with a hamburger drawer. Why: A product page with zero navigation on mobile fails the Slack-this-URL test the instant a prospect opens it on their phone, which is when all warm intros
  7. 7. Add at least two more content sections, specifically a "How It Works" step-by-step and a "Who This Is For" ICP section, to reach the six-section floor. Why: Current structure is hero, features grid, pricing, FAQ, footer, which is five tops,
  8. 8. Substantiate "Your books, done by morning" with a concrete mechanism in the body: what data the user provides, what the AI does overnight, and when they see results. Why: Honest copy standard; an unanchored overnight promise on a financial
  9. 9. Add a named social proof section with at minimum two real attributed quotes that include name, business type, and location. Why: Studio standard prohibits zero testimonials as much as fake ones; revoscape.com shows named users with their co
  10. 10. Explain what the $5 tier actually does versus the $199 tier before anyone sees the cards. Why: A 40x price range with no framing in between makes the low end look like a bait tier and the high end look arbitrary; pricing transparency is a T
  11. 11. Remove the `transform: scale(1.05)` plus `box-shadow: rgba(29,184,122,0.15)` combination on the featured pricing card and replace with a typographic "Most Popular" badge. Why: Studio standards explicitly ban identical gradient borders on ca
  12. 12. Build a structured footer with product links (pricing, FAQ), company links (about, contact), and a one-line liability note if the "done by morning" promise has conditions. Why: Every flagship in the portfolio (proxybox.us, revoscape.com, in
  13. 13. Document the navy/green palette as a deliberate variation from forest/gold/cream, with a comment in the CSS, or switch to forest/gold/cream. Why: `#0f1f3d` + `#1db87a` is a fintech-generic palette with no relationship to the studio's establ
  14. 14. Remove the duplicate `Plus Jakarta Sans` font load: it appears once in the page `<link>` tags and is referenced again inside the inline `<style>` block, and Inter is also loaded a second time after the shell already loaded it. Why: Double-l
  15. 15. Replace the green-circle trust badges with specific, verifiable facts: the name of the accounting standard it follows, the data encryption method, or the jurisdiction of the entity operating it. Why: Studio standard rejects big numbers with

white-label-document-collection-portal-for-law-fir

Aug 29, 02:05 · 10KB · 15 demands shown
  1. 1. The `<title>` tag reads "Wishdeal Factory · Pre-built AI businesses you can try live" -- that is the factory home title, not this product's title; replace it with a product-specific title naming the law firm use case before any indexing hap
  2. 2. The canonical URL in `<head>` points to `https://wishdeal.com/factory/` instead of this page's own URL; Google will treat this as duplicate content of the home page and will not rank the product page independently. Why: basic SEO hygiene re
  3. 3. The `og:url`, `og:title`, `og:description`, and `og:image` all resolve to factory home assets; every social share of this URL renders the wrong card. Why: proxybox and revoscape each carry product-specific OG cards with a real 1200x630 imag
  4. 4. The URL slug ends in "law-fir" -- it is truncated; fix the slug to the full intended phrase before Google indexes this broken string permanently. Why: a truncated slug signals a broken CMS pipeline and creates an unfixable canonical once cr
  5. 5. The `.top` nav element has no `position: sticky` and no `backdrop-filter: blur` in the stylesheet; apply the studio-standard sticky tinted nav immediately. Why: dailyunlock, revoscape, and voicetrail all demonstrate this as a non-negotiable
  6. 6. The `.num` stat blocks use `border-left: 3px solid var(--gold)` accent bars; remove them -- that pattern is explicitly banned by studio standards. Why: identical gradient borders and left accent bars are on the prohibited list.
  7. 7. Every large number in the numbers-grid and tick-card is unsourced; a law firm evaluating a document portal will not trust unjustified metrics, and attorneys are trained to interrogate evidence. Why: studio standard requires provenance or a
  8. 8. The hero tick-card renders a 3.6rem live counter as the main right-column visual; a cautious estate planning attorney does not care about a real-time widget counter -- replace it with a concrete client outcome (e.g., "Firms cut document-cha
  9. 9. There is no real photography anywhere in the accessible HTML; a law firm document portal hero must show an actual workflow image -- an attorney reviewing an upload screen, a signed document arriving, a client intake flow -- not a color bloc
  10. 10. The hero headline (once product-specific) must name a concrete attorney pain point, not describe a software category; "document collection portal" means nothing to a 54-year-old probate attorney drowning in client-uploaded JPEGs -- rewrite
  11. 11. There is no pricing section or visible link to a pricing page; law firm buyers will not request a blind demo for a Tier 2 tool. Why: Tier 2 standard requires pricing transparency on-page or one click away with a clear nav link.
  12. 12. There is no FAQ section; law firm buyers have compliance questions that will kill the deal if left unanswered -- add at minimum: data encryption standard, data residency location, state bar ethics compliance stance, breach notification poli
  13. 13. There are no named customer testimonials with attorney name, firm name, and practice area; a single anonymous quote or no quote does not pass the prospect test for a legal-market tool. Why: rootedmindsproject shows three named, role-specifi
  14. 14. The "white-label" claim in the product name is never illustrated; show what the portal actually looks like branded as "Johnson & Associates Client Portal" with a screenshot or mockup -- buyers need to see the white-label output, not read a
  15. 15. The page body word count almost certainly falls below 1200 words given the factory shell structure; law firm buyers research carefully before giving a vendor access to client documents -- the page must earn that trust with substantive copy.

white-label-document-collection-portal-for-law-fir

Aug 29, 01:31 · 9KB · 15 demands shown
  1. 1. The hero headline is "White-Label Document Collection Portal for Law Firms" -- a product descriptor, not a hook. Rewrite to lead with the outcome a managing partner cares about: time, money, or liability.
  2. 2. Both CTA buttons are `<button>` elements with no `href` or form target -- clicking "Start your free trial" and "Book a 20-minute demo" does nothing. Wire them to actual destinations before this page sees a prospect.
  3. 3. Every feature card in both the Problem and Solution sections uses identical `border-left: 4px solid #2A7D5B` -- the studio explicitly prohibits identical left accent bars. Differentiate with icons, numbered steps, or illustrated treatments.
  4. 4. There is no navigation element anywhere in the page. A sticky tinted nav with backdrop-filter blur is non-negotiable per studio standards.
  5. 5. Source Serif 4 + IBM Plex Sans is not Fraunces + Inter, and no variation is documented. Either switch to the studio pair or add a comment in the file explaining the deliberate deviation.
  6. 6. The palette is navy + green + gray. There is no gold and no cream. The studio requires forest/gold/cream or a documented alternative. This reads like a fintech template, not a law firm tool.
  7. 7. The hero background is a CSS gradient. The Unsplash photo (`photo-1552664730-d307ca884978` -- a generic "team collaborating" shot) sits below the CTAs as decoration. Real photography belongs in the hero itself, not as an afterthought beneat
  8. 8. The Unsplash image is a generic office meeting shot that could be for a project management app, an HR tool, or a pizza chain. Replace it with either a product screenshot showing the branded portal or a photo that signals "law firm" without
  9. 9. The "proof" section is a dark block with no name, no firm, no role, no outcome number. "2-3 weeks faster" appears twice with zero attribution. Revoscape shows three named testimonials with photos and venue logos. This page shows none.
  10. 10. The "Case files open 2-3 weeks faster" claim is used in the hero subhead without any source. Either anchor it to beta data ("based on 12 pilot firms, Q1 2025") or remove it -- honest copy is a studio standard.
  11. 11. The pricing section appears to be a single `pricing-box` div. A Tier 2 SMB tool needs three named tiers with explicit feature differentiation so a buyer can self-qualify without booking a call.
  12. 12. No FAQ section exists in the visible HTML. Law firm buyers have blocking questions before any demo: HIPAA compliance posture, what happens to documents after case close, whether clients can re-upload rejected files, how pricing works per se
  13. 13. No sub-pages are linked. A Tier 2 product needs at minimum a pricing page and an FAQ. The footer appears to have one green link and nothing else.
  14. 14. The `<span id="main" role="main"></span>` immediately after the skip link is an empty inline span, not a `<main>` element. The actual page content is outside any landmark element. Fix the accessibility markup.
  15. 15. The problem section and solution section use the same three-card grid with the same card style. A reader scanning on mobile cannot tell where the problem ends and the solution begins without reading every word. Create visual contrast betwee

bookkeeper-ai

Aug 29, 01:00 · 11KB · 15 demands shown
  1. 1. Replace Plus Jakarta Sans on every `h1`, `h2`, `h3`, and `.logo` with Fraunces -- the WD_SHELL_CSS_v1 block already loads Fraunces and Plus Jakarta Sans is an undocumented deviation that actively overrides the design system. Why: Fraunces +
  2. 2. Add `position: sticky; top: 0; backdrop-filter: blur(12px)` to the header -- the current header is static with a hard `#0f1f3d` background and scrolls away immediately. Why: sticky tinted nav with backdrop blur is a studio floor requirement
  3. 3. Put a real photograph in the hero -- the hero is a plain `linear-gradient(135deg, #0f1f3d 0%, #1a2d4a 100%)` with no image whatsoever; add a photo of a small-business owner reviewing a P&L, a tidy desk with a laptop, or a real dashboard scr
  4. 4. Add real photography or a product screenshot to at least two feature-block sections -- every feature card is a white CSS box with no visual; proxybox.us uses a real device render in every split-content section. Why: stock SVG icons are not
  5. 5. Document or correct the navy/green palette (`#0f1f3d` + `#1db87a`) -- it is not the forest/gold/cream palette and no build note marks it as a deliberate brand variation. Why: undocumented palette deviations fail the studio standard.
  6. 6. Remove the duplicate Inter font load -- Inter is loaded once by the WD_SHELL_CSS_v1 block and a second time in a separate explicit `<link>` tag on the same page. Why: redundant font calls waste bandwidth and signal a page built ignoring its
  7. 7. Give mobile users a navigation -- `nav { display: none; }` at 768px and below means the page has zero navigation on the device your SMB customer is most likely using; add a hamburger or a sticky bottom CTA bar. Why: hiding the entire nav on
  8. 8. Rewrite the headline and subheading to speak the language of a 52-year-old restaurant owner or HVAC contractor -- "Autonomous Accounting for SMBs" is insider SaaS copy; the customer's phrase is "I have no idea if I made money last month." W
  9. 9. Fix the `<title>` tag double space: `Bookkeeper AI - Autonomous Accounting for SMBs` has two spaces before the dash. Why: a sloppy title tag undermines SEO and signals low production quality.
  10. 10. Add `<meta property="og:image">` and Twitter card meta tags -- the JSON-LD references an OG image URL but the actual `<meta>` tags are absent from the `<head>`, meaning sharing the URL produces a blank preview card. Why: missing OG tags fai
  11. 11. Strip the trust badges or replace them with verifiable claims -- `.badge-icon` elements are CSS green circles with text inside; they are not real certifications, are not linked to any compliance page, and have no provenance. Why: honest cop
  12. 12. Add a social proof section with named, attributed testimonials -- there is no testimonial section at all; revoscape.com has three named customers with photos and a venue logo bar above the fold. Why: a Tier 2 SMB tool requires at least one
  13. 13. Vary the card border treatment -- every `.feature-block` has the identical `border: 1px solid #eef0f4`; use shadow-only or differentiate by section context. Why: identical borders on all cards is an explicit studio anti-pattern.
  14. 14. Change the featured pricing card from a colored `border-color: #1db87a` to a scale + shadow treatment -- the green border plus green-tinted box-shadow is double-signaling with an accent color that violates the cards rule. Why: no identical
  15. 15. Bring the page to at least 1,200 body words -- the current section structure (hero + features + pricing + FAQ + footer) cannot reach 1,200 words at this density; add a "How it works" walkthrough or a "Who it's for" ICP section. Why: 1,200+

contract-ai

Aug 29, 00:44 · 10KB · 15 demands shown
  1. 1. The product is called "Contract AI" in the `<title>` and page HTML but "Inkwell" in the JSON-LD, OG tags, and Twitter card. Pick one name and use it everywhere before a prospect screenshot-shares it and the brand looks like a staging error.
  2. 2. The hero is a dark-blue gradient rectangle with text and a button. There is no photograph anywhere in the HTML. Put a real photo in the hero: a professional reviewing a printed contract, a desk with a signed NDA, anything true. proxybox.us
  3. 3. The entire palette is navy (#0f2b4a) and fire-engine red (#e84c2f) over cold gray (#f8f9fa). This is generic 2019 SaaS. Either commit to forest/gold/cream or write down the deliberate palette variation in the build manifest. Undocumented de
  4. 4. Every feature card has `border-left: 4px solid #c84a1f`. Left accent bars are explicitly forbidden. Remove them from all cards.
  5. 5. The metrics block displays three large red numbers with no stated source, no methodology, no provenance. State where each number came from or delete the section. Honest copy is non-negotiable.
  6. 6. Pricing ($5 to $199, three tiers) appears only in the JSON-LD structured data. There is no pricing section on this page. A prospect evaluating a contract analysis tool cannot see what it costs without clicking through to a separate unlock p
  7. 7. For a tool handling legal documents, the absence of a security or privacy stance is a hard stop for any business buyer. Add a brief section: where documents are processed, whether they are stored, whether they leave the user's account. Revo
  8. 8. The feature grid and the feature checklist cover identical ground split across two sections. Replace one of them with a genuine workflow section showing the before/after: contract goes in, flagged risks come out. The product's output is its
  9. 9. The `benefit-section` has a text column and a visual column. The visual column contains no image in the visible HTML. Put a real screenshot of the product or a photo of a flagged contract in that column, or remove the two-column layout enti
  10. 10. "Intelligent Contract Analysis and Risk Flagging" names a technology category, not a buyer. Revoscape's title says "for Property Managers." Rewrite the H1 and title tag to name the specific person this tool is for: the SMB owner, the freela
  11. 11. There are no testimonials anywhere visible on this page. One named person at a real company with a real outcome is the floor for Tier 2. "We caught a $12,000 auto-renewal clause on day one" from a real business name does more than any featu
  12. 12. The body background (#f8f9fa) is a cold gray that reads as "forgot to set a background." The studio cream standard is warm (#faf7f0 range). This is a small detail that tells a prospect the palette was not deliberately chosen.
  13. 13. The page has no in-page navigation anchors. A prospect landing here cannot jump to pricing or FAQ. Add anchor links in the nav or a sticky jump-bar so the page does not require blind scrolling on mobile.
  14. 14. This product has no sub-pages specific to Contract AI: no FAQ, no how-it-works, no comparison, no legal/privacy page. For a Tier 2 SMB tool handling sensitive documents, a standalone FAQ page answering "is my data safe, what file types work
  15. 15. The CTA button color (#e84c2f) is borrowed from a different brand's danger state. It clashes with the navy header. If the palette is navy-and-red, the CTA should be the brightest, most intentional point of that system, not a color that read

afterhours

Aug 29, 00:05 · 9KB · 15 demands shown
  1. 1. Replace the plain-white hero background with a real photograph of the scenario this product solves -- a trade contractor checking a missed call at 10pm, a van in a dark driveway. Why: Every reference flagship (revoscape, rootedmindsproject,
  2. 2. Strike "+35% More Qualified Leads," "82% Show Rate," and "3x Faster Scheduling" or add a parenthetical source in plain text next to each number -- pilot data, industry study, or your own beta cohort. Why: Honest copy standard bars big numbe
  3. 3. Remove "Service businesses lose 40% of after-hours leads to competitors" or cite the source inline. Why: Same standard -- one unsourced claim is a mistake, four on one page is a pattern that kills credibility.
  4. 4. The page body is under 500 words; a Tier 2 product page being actively sold requires 1200+. Why: Studio standard is explicit -- write the copy that earns the scroll.
  5. 5. Add a pricing section with at minimum a "starting at $X/month" anchor. Why: Tier 2 demands pricing transparency, and a service business owner who can't find a price range will not fill out a form.
  6. 6. Add a FAQ section with at least 8 questions a plumber or HVAC owner would actually ask -- does it work with my existing number, what happens if the agent can't answer the question, what do I do with the lead sheet. Why: Tier 2 standard requ
  7. 7. "Service businesses" names no one; rewrite the hero to speak to one named trade (HVAC, plumbing, landscaping) and let the subheadline broaden from there. Why: rootedmindsproject.org names its exact ICP ("families raising children whose brai
  8. 8. "AfterHours" is not an H1 -- it is a product name; move "The night desk for service businesses" into the H1 position and demote the brand name. Why: The subtitle is the strongest copy on the page and it is wasted in a secondary slot.
  9. 9. The ✓ checkmarks in feature card H3s are text characters standing in for icons -- replace with a numbered step flow (1, 2, 3, 4) or real SVG icons that reinforce the voice/phone concept. Why: Studio standard explicitly prohibits stock SVG i
  10. 10. The page's hero uses a `<header>` element, making two `<header>` elements in the document -- the WD shell nav is already a `<header class="wd-shell-nav">`. Convert the page hero to `<section class="hero">`. Why: Invalid HTML semantics break
  11. 11. The CTA "See How It Works" links to `#get-started` but no element on the page has `id="get-started"` -- the link goes nowhere. Why: A broken anchor on the primary hero CTA means the first thing a prospect clicks fails silently.
  12. 12. The three stat boxes are stacked vertically in a single column; display them in a three-column horizontal grid. Why: Every reference site (revoscape, spearplus, proxybox) uses horizontal stat bars -- a vertical stack reads like a list, not
  13. 13. A voice intake product has no audio demo anywhere on the page -- add a 30-second embedded sample call or a waveform graphic with a transcript snippet showing the agent in action. Why: Asking someone to trust a voice agent they have never he
  14. 14. Add OG meta tags (`og:image`, `og:description`, `twitter:card`) to the page head. Why: Right now if a prospect pastes this URL into a text message or Slack, no preview renders -- the Slack-stranger test fails at the link-share step.
  15. 15. "Hand Off Warm" card promises a "complete lead sheet" but never says how it arrives -- name one concrete delivery method (email to the owner, Slack notification, CRM push). Why: A service business owner needs to know where to look in the mo