Wishdeal Factory
Foreman feed · cross-LLM critiques

3830 reports, 57369 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

Oct 19, 00:47 · 10KB · 15 demands shown
  1. 1. The hero has zero photography - it is text on a cream background with no image whatsoever. Add a real screenshot of the product dashboard or a contextual photo of a small business owner reviewing their books. Why: the standard requires real
  2. 2. The nav is solid white (`background: white`) with no `backdrop-filter`. Replace it with `background: rgba(248,246,241,0.85); backdrop-filter: blur(12px)` and a forest-tinted tint. Why: sticky tinted nav with backdrop-filter blur is non-nego
  3. 3. The entire primary palette is corporate blue (`#2d6ea8`) while the favicon uses forest green (`#1f3a2e`). The brand is split between two unrelated color systems. Commit to the forest/gold/cream palette or document the variation explicitly.
  4. 4. Every feature card uses a naked emoji as its visual (`font-size: 2.5rem`). Replace them with real product screenshots, annotated UI details, or contextual photos. Stock SVG icons and emoji are not substitutes for photography in section feat
  5. 5. There is no social proof anywhere on the page - no testimonials, no logos, no named clients, no review count. Add at least one named testimonial with a real business type ("Sara M., freelance accountant, 3 clients"). Why: Tier 2 SMB tools r
  6. 6. The pricing `.price` figures are rendered in `#2d6ea8` at 2.5rem - this is a neon hero number applied to the pricing section. Render price figures in the body dark color (`#1c2431`) or forest accent. Why: "No neon hero numbers" is an explic
  7. 7. There are five substantive sections: hero, features, benefits, pricing, final-cta. Six-plus sections is the floor. Add a "How it works" section (connect → analyze → report) and a FAQ. Why: section count standard; voicetrail.ai and spearplus
  8. 8. The headline "Instant Financial Clarity for Your Books" names no customer and describes no pain. Rewrite it to name the actual buyer - a freelancer buried in receipts, a restaurant owner who hasn't reconciled in 90 days. Why: honest copy st
  9. 9. There is no "How it works" process section. A bookkeeping AI requires an integration explanation: what connects to it, how the AI reads the data, what the output looks like. Why: buyers of financial software need to trust the mechanism befo
  10. 10. The footer is a single centered row. It has no product links, no company links, no legal footer, no sub-pages whatsoever. Build a three-column footer with product nav, company nav, and legal. Why: proxybox.us and spearplus.com both use mult
  11. 11. No sub-pages are linked anywhere - no /faq, /pricing, /about, /security. For a bookkeeping AI handling financial data, the absence of a security or privacy page is a conversion killer for any business owner with half a brain. Add at minimum
  12. 12. The body word count across hero + features + benefits + pricing is almost certainly under 800 words given the thin card structure. The floor for a sold landing page is 1200+. Expand the "How it works" and FAQ sections to reach it. Why: 1200
  13. 13. The `.final-cta` section has `border: 1px solid #e8e5df; border-radius: 6px` - the same visual weight as a `.feature-card`. It does not read as a conversion moment. Give it a forest-green background or a gold accent band to signal finality.
  14. 14. The `.pricing-card.highlight` lifts 10px with `position: relative; top: -10px`, which creates a misaligned grid on mobile and is a visual hack from 2015. Mark the recommended tier with a badge and a border, not vertical displacement. Why: r
  15. 15. The benefits section and the features section are structurally identical - both are grids of white cards with a title and a paragraph. The buyer cannot distinguish what is a feature and what is a benefit. Redesign one as a two-column narrat

contract-ai

Oct 18, 22:36 · 8KB · 15 demands shown
  1. 1. The hero section has no photography, no background image, and no visual context -- it renders as white text on a cream void; add a real photograph of a person reviewing a contract at a desk before this page is shown to anyone.
  2. 2. Every `.grid-image` slot is a literal CSS gradient placeholder (`linear-gradient(135deg, #e8ecf0 0%, #d4dce8 100%)`) with a centered label -- these are unfinished design comps, not a shipped page; replace each with a real contextual photo.
  3. 3. The nav is `background: #ffffff` with no `backdrop-filter` blur -- the standard requires a sticky tinted nav with blur; proxybox.us and revoscape.com both ship this correctly and it is not present here.
  4. 4. The `<title>` says "Contract AI" and the `og:title` says "Inkwell" -- every touchpoint (title tag, OG tags, hero, nav, footer) must use one name, not two.
  5. 5. The video-banner links to `explainer.mp4` as a bare relative path -- either verify that file exists at that exact URL or remove the banner, because a dead link in the first visible element kills credibility before the hero loads.
  6. 6. Feature cards are text-only with no iconography or imagery -- vendoriq.vip gives every feature card a visual anchor; three walls of small gray text in identical white boxes is not feature communication.
  7. 7. There is no social proof section anywhere -- a tool that touches legal documents and asks people to trust its AI analysis needs at minimum three attributed quotes from named users before a prospect will enter a credit card number.
  8. 8. Pricing exists only in buried JSON-LD schema (`$5-$199`); there is no visible pricing section on the page -- a Tier 2 SMB tool requires pricing transparency on the landing page, not hidden metadata.
  9. 9. The page likely falls below 1200 body words based on the visible section structure -- add enough copy to surface for "AI contract review," "contract analysis software," and "review NDA online" search queries.
  10. 10. The page defines a custom `nav { background: #ffffff }` CSS block while also injecting `WD_SHELL_NAV_v1` -- this renders two navigation bars simultaneously; remove the inline nav CSS entirely and rely on the shell.
  11. 11. There is no "how it works" section -- a prospect landing here does not know whether they paste text, upload a PDF, or connect their email client; add a numbered three-step walkthrough before the feature grid.
  12. 12. The `<title>` promises "Negotiation" -- if this tool only analyzes contracts and flags clauses, calling it "Negotiation" is dishonest copy that will generate refund disputes; fix the title to match actual capability.
  13. 13. No ICP language is visible anywhere -- the copy must name the buyer (freelancer, small business owner, solo founder) so a prospect immediately self-identifies instead of reading generic AI pitch language.
  14. 14. No section shows example output -- the first question every prospect has is "what does an analysis actually look like?"; a single annotated screenshot or simplified mockup answers it before they bounce.
  15. 15. The nav hover color is `#c94b35` (brick red) -- this is not the forest/gold/cream palette; align all interactive states to the established palette.

bookkeeper-ai

Oct 18, 21:53 · 10KB · 15 demands shown
  1. 1. The hero contains zero photography. Real photography is required in every hero, no exceptions. Revoscape.com anchors its hero with a full-bleed venue photograph; this page shows nothing but centered text on a cream background.
  2. 2. Feature blocks use emoji icons rendered via `.icon { font-size: 2.5rem; }`. Three emoji characters are not feature photography. Replace each with a real contextual image: a screenshot of the anomaly-flagging UI, a photo of someone at a desk
  3. 3. The nav is `background: white` with a border. There is no `backdrop-filter` and no tint. Studio standard requires a sticky tinted nav with backdrop-filter blur. See dailyunlock.us, which runs `backdrop-filter: blur(24px)` on a transparent b
  4. 4. The entire color system uses `#2d6ea8` corporate blue as its primary. This is a full palette departure from forest/gold/cream. Either adopt the palette or write a one-line documented reason this product gets a variation. Undocumented deviat
  5. 5. There are four content sections: hero, features, benefits, pricing. The floor is six. Add "How It Works" (the three-step workflow) and "FAQ" at minimum before this page is considered complete.
  6. 6. There is no FAQ section. For a Tier 2 bookkeeping AI, buyers will have three specific questions before purchasing: how does my data connect, what happens to my books if I cancel, and how accurate is the anomaly detection. None of those ques
  7. 7. There is no social proof section. Not one named person with a title and company has reviewed this product. An SMB owner spending money on financial software does not buy without evidence. Even one real testimonial with a name, title, and ci
  8. 8. No sub-pages exist or are linked. The nav and footer must point to real destinations: /faq, /pricing, /security, /about. The Slack-this-URL-to-a-stranger test fails immediately when there is nowhere to go after the hero.
  9. 9. "Instant Financial Clarity" and "Real-time clarity without spreadsheet drudgery" are dead SaaS copy. Rewrite the hero headline and subhead for the specific buyer: a small business owner who found a $4,000 discrepancy at tax time because the
  10. 10. Fonts are loaded twice. The `WD_SHELL_CSS_v1` block already pulls Fraunces and Inter, then a second `<link href="https://fonts.googleapis.com/css2?family=Fraunces...">` tag loads them again inline. Delete the duplicate.
  11. 11. The `.final-cta` section is a floating white card with `border: 1px solid #e8e5df`. It is visually identical to a feature card. The final CTA must be a full-width, visually distinct band, not a smaller version of the section above it.
  12. 12. The highlighted pricing card uses `border: 2px solid #2d6ea8`. If you are keeping blue as the primary, that is defensible, but the recommended plan should be visually warmer and more emphatic than a border color change. Give it a background
  13. 13. The benefit items (`.benefit-item { background: #f8f6f1; border-radius: 4px; }`) are styled nearly identically to the feature cards. Two sections with the same card grammar in sequence make the page feel like a single feature section that c
  14. 14. There is no "How It Works" section. A bookkeeping AI requires the buyer to understand the workflow before they trust it: connect your accounts, the AI reads and categorizes, you review flagged anomalies. Without this, the page answers "what
  15. 15. There is no mention of integrations anywhere on the page. QuickBooks, Xero, or FreshBooks compatibility is the first question any small business owner has when evaluating a bookkeeping tool. Its absence is a conversion stopper, not a missin

world-time-scrubber

Oct 18, 21:24 · 9KB · 15 demands shown
  1. 1. The `.hero-image` is a CSS gradient placeholder -- `linear-gradient(135deg, #f5f3f0 0%, #ede9e2 100%)` with gray label text -- not a photograph. Replace it with an actual screenshot of the scrubber UI or a real photo of someone managing tim
  2. 2. The primary CTA is `background-color: #1c1c1c` (coal black). The factory standard is forest green (`#1f3a2e`). Fix it -- every Tier 2 factory build uses the forest/gold/cream trio and this button breaks it on the most visible interactive el
  3. 3. Gold is absent from the entire visible palette. Not one accent line, badge, price highlight, or hover state. The tri-color identity requires it -- add at minimum a gold underline on the hero `<h1>` or a gold border on the pricing-box.
  4. 4. Fraunces is loaded twice: once correctly via `WD_SHELL_CSS_v1` with full weight axes (`wght@9..144,400;9..144,500;9..144,600;9..144,700`) and once via a redundant inline `<link>` that loads only `opsz@9..144` with no weight axis, risking FO
  5. 5. The page defines a massive inline `<style>` block that re-declares `header`, `h1`, `h2`, `section`, `p`, `ul`, `li`, and `footer` rather than extending factory.css. This is why the palette is already drifting. Remove inline overrides and wo
  6. 6. The hero `<h1>` is sized at `2.5rem` -- the same scale as a mid-page subheading. A product hero demands 3.5--4rem on desktop; compare how spearplus.com's headline commands the screen before the user reads a single word of body copy.
  7. 7. The tagline "Pull the clock. Every timezone snaps into place." names no buyer. A dev team? A remote-first EA? A sales manager covering three continents? Add one ICP noun to the subhead so a stranger knows in two seconds whether this is for
  8. 8. The `@type` in schema.org is `Product` with `category: "general saas"` -- both wrong for a web app. Use `@type: SoftwareApplication` with `applicationCategory: "UtilitiesApplication"`.
  9. 9. The schema `description` is the seven-word tagline verbatim. Write two sentences that include what it does, who it's for, and one measurable outcome.
  10. 10. `.cta-button:hover` changes background-color with zero CSS transition. Add `transition: background-color 0.15s ease` -- without it the hover is a hard flash that reads as broken.
  11. 11. `.pricing-box { background-color: white }` sits inside a `#f8f7f4` cream-background page and jolts the eye. Match it to the warm cream or use a very light forest tint to keep the palette continuous.
  12. 12. `border-radius: 2px` on the CTA, `4px` on the hero image, `4px` on the pricing box -- three values, no system. Pick one radius token and apply it everywhere.
  13. 13. The OG image points to `/factory/og/world-time-scrubber.png`. If this file does not exist as a static asset, every social share returns a broken card. Confirm the file is live before calling this page public.
  14. 14. The subnav has a "Case Studies" link. A Tier 2 tool priced at $5 entry with no named users visible should rename this "Examples" or "Use Cases" -- promising case studies you cannot back with real named teams erodes trust faster than having
  15. 15. The `wd-hero-empty-fix` CSS rule (`display:none!important` on an empty `.hero-image`) confirms the hero image div may render empty and be hidden entirely, leaving the page's top fold as nav + headline + two buttons + nothing visual. That is

company-brain

Oct 18, 20:27 · 10KB · 15 demands shown
  1. 1. Replace every `font-family: 'Space Grotesk'` declaration with `font-family: 'Fraunces', serif` - the shell already loads Fraunces but the build overrides it with a font that belongs to a different product family. Why: Fraunces + Inter is th
  2. 2. The hero gradient (`#141c2e → #1a1f2e`) is a two-shade-of-charcoal trick that reads as a generic SaaS template - replace with `#1f3a2e` forest or document the deliberate deviation. Why: forest/gold/cream is the palette standard; the current
  3. 3. The hero section has no photography of any kind - add a real product UI screenshot or an in-context workplace photo as the hero visual before any other changes are made. Why: real photography in every hero is a hard requirement; revoscape.c
  4. 4. The page has three content sections (hero, features, use cases) plus a footer - six sections is the floor; add at minimum a how-it-works walkthrough, a pricing section, and an FAQ before considering this page shippable. Why: Tier 2 explicit
  5. 5. The CTA button color is `#4f46e5` indigo, the default Tailwind indigo - replace with a gold or forest-adjacent accent that belongs to this palette, not Bootstrap's. Why: no flagship in the reference set uses blue-purple as its primary actio
  6. 6. The body background `#f0f2f7` is a cold blue-gray that fights the forest/gold/cream palette - replace with `#faf7f0` cream or `#f5f2ec` warm off-white. Why: cream is the standard surface color used across proxybox, rootedminds, and investwi
  7. 7. The feature cards all share the identical `#f9fafc` fill and `#e2e8f0` border with no photography, no icon, no visual hierarchy between them - differentiate at least the lead card with a real image or a distinct treatment. Why: identical gr
  8. 8. No pricing section exists despite schema declaring a `$5-$199` range - show the tiers with real names, prices, and what each includes, on this page. Why: Tier 2 requires pricing transparency; a prospect who cannot see price does not convert
  9. 9. There is no FAQ section anywhere on the page - add one with at least five questions that address the actual buying objections (data security, setup time, integrations, who owns the data). Why: Tier 2 standard explicitly names FAQ as require
  10. 10. The hero headline "Knowledge at the Speed of Thought" is a tagline for a category, not a product - rewrite to name the exact buyer and the exact pain replaced ("Your onboarding doc is on Slack. Your process is in someone's head. Company Bra
  11. 11. There is no social proof on the page - not a name, not a quote, not even a "used by X teams" line - add at minimum one named testimonial with a real title. Why: rootedmindsproject and revoscape both lead with named, photographed social proo
  12. 12. The meta description is six words ("Your organization's knowledge, finally searchable") - rewrite it to 140-160 characters naming the product category, the buyer, and the outcome. Why: the OG description is what a prospect reads before clic
  13. 13. The use cases section is visually identical to the features section - same card weight, same white fill, same font - a reader scanning at speed cannot tell they have moved into different content. Add a section label, change the background,
  14. 14. The product name appears as "Company Brain" in the `<title>`, "CompanyBrain" in the schema, and the page copy should be checked for a third variant - pick one capitalization and use it everywhere including the nav subnav, the schema, and th
  15. 15. The footer is a single dark bar with one line of text and no links - add at minimum a link to pricing, FAQ, and the factory catalog. Why: proxybox and rootedminds both use the footer as a secondary navigation layer; a dead-end footer is a c

bookkeeper-ai

Oct 18, 20:02 · 9KB · 15 demands shown
  1. 1. Replace `Plus Jakarta Sans` on all `h1,h2,h3` with `Fraunces` - the shell already loads it via `WD_SHELL_CSS_v1`, the font is a wasted HTTP request, and the studio standard is non-negotiable without documented deviation.
  2. 2. Remove every `border-left:4px solid #1db87a` from `.value-prop` cards - left accent bars are explicitly banned by studio standards, and every flagship (proxybox, revoscape) uses shadow or border-radius to differentiate cards, not a colored
  3. 3. Make the `header` sticky with `position:sticky; top:0; backdrop-filter:blur(12px)` and a translucent background - the current `background:#0f1f3d` is a static block with no blur, and every flagship reference from voicetrail to spearplus use
  4. 4. Replace the `linear-gradient(135deg,#0f1f3d...)` hero background with a real photograph - a small business owner at a desk, receipts in frame, something that says "your actual work" - no photography is in the hero or any visible section, vi
  5. 5. Swap the body background from `#eef2f7` (icy blue-grey) to a warm cream like `#faf7f0` - every studio flagship uses warm neutrals; the current background makes the page read like a bank portal, not a product.
  6. 6. Rewrite the page title and hero headline away from "Modern CPAs" - the actual buyer of bookkeeper AI automation is the SMB owner, not the CPA; a CPA sees AI automation as a threat to their billing hours, not a feature.
  7. 7. Kill the `background:#1db87a` on `.cta-section` - a full-width neon green block is the palette equivalent of a foghorn; revoscape and proxybox both use dark/contrast CTA sections with real copy and a contained button, not a painted wall.
  8. 8. Add a pricing section directly on the page - the JSONLD schema already declares three tiers ($5-$199) but they appear nowhere in the HTML; at Tier 2 pricing transparency is mandatory and hiding it breaks trust on first visit.
  9. 9. Add at least 2 more content sections to reach the 6-section floor - currently: hero, value-props, features, CTA, footer is 4 sections; add a "how it works" step section and an FAQ to meet the minimum.
  10. 10. Fix the `.cta-section button` - it is a `<button>` element with no form or JS action, meaning clicking "Get Started" does nothing; either make it an `<a href="...">` or wire an actual navigation handler.
  11. 11. Verify and fix the `explainer.mp4` link in the video banner - it references a relative path `explainer.mp4` which almost certainly 404s; either point to the real video URL or remove the banner entirely rather than advertising a dead link.
  12. 12. Add a social proof section - no testimonial, no logo bar, no named customer exists on this page; investwithdreams and revoscape each show named faces with titles and company context; even one real quote from a real user beats zero.
  13. 13. Add photography to the features section - `.feature-card` elements are text-on-`#f9f9f9` boxes with `border:1px solid #ddd`, which is the visual equivalent of a spec sheet; voicetrail and proxybox both show product UI screenshots or context
  14. 14. Add an FAQ section with at least 5 real questions - "Will this replace my bookkeeper?", "How does it handle receipts?", "What integrations does it support?", "What if it makes an error?", "Is my financial data secure?" are the questions a b
  15. 15. Write at least 1,200 body words - the current page structure with 3-sentence cards and a tagline headline is well under 400 words; a Tier 2 product that costs up to $199/month needs substantive copy to earn the click.

bookkeeper-ai

Oct 18, 19:04 · 10KB · 15 demands shown
  1. 1. The header uses `h1,h2,h3{font-family:'Plus Jakarta Sans',sans-serif}` while Fraunces is loaded in the shell but never applied to headings -- switch to Fraunces for display headings or document why Plus Jakarta Sans was chosen. Why: studio
  2. 2. The nav is `background:#0f1f3d` with no `position:sticky`, no `backdrop-filter`, no tint transition on scroll -- make it sticky with backdrop-blur. Why: non-negotiable studio standard; proxybox.us and revoscape.com both implement this corre
  3. 3. The hero is a pure CSS gradient (`linear-gradient(135deg,#0f1f3d 0%,#1a2d4a 100%)`) with no photography -- put a real photo of a human working at a desk, or a real accounting interface, behind the headline. Why: real photography in every he
  4. 4. Every `.value-prop` card has `border-left:4px solid #1db87a` -- remove all left accent bars unconditionally. Why: explicitly banned by studio standards, no exceptions.
  5. 5. The palette is navy `#0f1f3d` + green `#1db87a` + blue-gray `#eef2f7`, which diverges from the forest/gold/cream standard without any documented rationale -- document the override or align to the standard. Why: undocumented palette deviatio
  6. 6. The ICP is split between the `<title>` ("Modern CPAs") and the OG tagline ("Your books, done by morning") -- the hero headline must commit to one buyer and speak directly to their specific pain, not both. Why: a CPA buying a white-label too
  7. 7. The section count visible in the HTML is hero, value-props, features, CTA band, footer -- that is five, below the six-section floor; add at minimum a social proof section and a how-it-works walkthrough section. Why: studio minimum is 6+ sec
  8. 8. The `about/`, `pricing/`, `faq/`, `integrations/`, `vs/`, `how-it-works/`, and `case-studies/` sub-pages exist on disk but the product nav does not link to any of them -- add a product-scoped nav that exposes pricing, how it works, FAQ, and
  9. 9. There is no pricing information on the landing page itself, only on a buried sub-page -- surface the plan names and price points (the JSON-LD already lists $5-$199) directly on the main page with a link to the full pricing page. Why: Tier 2
  10. 10. There is no social proof section anywhere visible -- add at minimum a "used by" logo bar or a single named testimonial with a real title and company; if no named social proof exists yet, use a quantitative claim with provenance ("X invoices
  11. 11. The feature card body text is `font-size:0.9rem` -- bump to at minimum `1rem` (16px); text smaller than the body baseline reads as fine print, not feature benefit copy. Why: vendoriq.vip and proxybox.us both set feature copy at full body si
  12. 12. The hero CTA buttons say "Get Early Access" and "Watch Demo" -- these are generic SaaS placeholders; rewrite the primary CTA to reflect the specific action ("Connect Your QuickBooks" or "Run My First Reconciliation") and the secondary CTA t
  13. 13. The video banner (`explainer.mp4`) sits above the shell nav as the very first rendered element -- move it below the nav or integrate it as a secondary CTA inside the hero; an announcement bar above the nav is for time-sensitive promotions,
  14. 14. The feature cards are all `background:#f9f9f9` with `border:1px solid #ddd` -- identical styling with no hierarchy; at minimum, make the flagship feature card visually distinct through size, a real screenshot, or contrasting background. Why
  15. 15. The page has no competitive differentiation copy -- add a single sentence or callout that names the specific category weakness this product fixes (e.g., "Unlike Botkeeper, no minimum seat requirement") so a visitor who has already evaluated

iroh-p2p-video-collaboration

Oct 18, 18:08 · 10KB · 15 demands shown
  1. 1. Replace Space Grotesk with Fraunces for every heading on the page - the font is a non-negotiable studio standard documented in the shell, and this page overrides it entirely with its own `<style>` block. Why: Studio standard (Fraunces serif
  2. 2. Rip out the dark-navy + neon-cyan palette (#0f1923 / #00c2e0) and replace with Forest/gold/cream - cyan number badges and cyan CTAs make this look like a DigitalOcean clone, not a Wishdeal Factory product. Why: Studio standard (no rainbow p
  3. 3. Drop the duplicate inline `<style>` block entirely and style through factory.css - the page loads Space Grotesk AND Fraunces via two separate font requests, then ignores Fraunces in the cascade. Why: Basic asset hygiene; revoscape.com ships
  4. 4. Put a real photograph in the hero - a laptop screen showing a P2P connection diagram, two people on a video call without a central server icon, anything photographic. Right now the hero is a gradient rectangle with text. Why: Studio standar
  5. 5. Add a product screenshot or topology diagram to at least two of the six feature cards - "Privacy-First" and "Zero Infrastructure" are currently empty text boxes with no visual evidence. Why: proxybox.us shows device photos inside feature bl
  6. 6. The sticky shell nav is present but the page renders its own static `<header>` gradient block directly below it, creating two stacked navs - remove the page-level header and move the headline + CTA into a proper hero section below the shell
  7. 7. Add a section explaining who "iroh" is and why the name - a stranger reading this URL has no idea if iroh is a company, an open-source library, a fork, or a product Wes built. Why: The Slack-this-URL-to-a-stranger test; proxybox.us names th
  8. 8. The hero CTA "Get Started" links nowhere actionable for a developer - replace it with "Read the Docs" or "npm install iroh" with an actual code snippet below the fold so the developer audience gets an honest first impression. Why: revoscape
  9. 9. Write at least 1,200 body words - current visible copy is roughly 400 words across hero, three feature cards, three steps, two pricing cards, and three FAQ answers. Why: Studio standard (1200+ body words on any page being sold).
  10. 10. The FAQ is capped at max-width 600px centered in a 1200px container - it looks like a forgotten afterthought. Expand to at least 800px and add four more questions specific to P2P video: latency expectations, firewall traversal, mobile suppo
  11. 11. Add a "How it compares" section naming Zoom, Google Meet, and Jitsi by name - a developer evaluating a P2P video library will ask "why not just embed Jitsi?" and this page has no answer. Why: Studio standard (real internal links + compariso
  12. 12. The three pricing cards are visually identical - same white box, same shadow, same check marks in cyan. Visually distinguish the recommended tier with a forest-green border, a "Most Popular" label, or a size difference. Why: Studio standard
  13. 13. The footer is a single line with one link - add at minimum: copyright, docs link, GitHub link (if open source), privacy policy, and a one-line company attribution. Why: every flagship site (investwithdreams, revoscape, proxybox) ships a mul
  14. 14. Remove the three circular cyan step-number bubbles - filled circles used decoratively are the orb anti-pattern applied to numbers. Replace with plain numerals in Fraunces, large and left-aligned. Why: Studio standard (no orb backgrounds).
  15. 15. Add at least one named, attributed testimonial from a real developer who has used iroh or P2P video in production - the social proof section is entirely absent, and for a Tier 2 tool this is the single largest trust gap. Why: revoscape.com

company-brain

Oct 18, 17:17 · 8KB · 15 demands shown
  1. 1. The hero contains zero photography. It is a flat dark-navy gradient with centered text. Add a real product screenshot, workspace photo, or ambient image that communicates what "company knowledge" looks like in use. See proxybox.us, which le
  2. 2. Every heading on the page uses `Space Grotesk`, not `Fraunces`. This is an undocumented deviation from the studio font standard. Either switch to Fraunces for display headings or write a single-line comment in the file explaining the except
  3. 3. The palette is cold navy (`#141c2e`), blue-gray body (`#f0f2f7`), and indigo CTAs (`#4f46e5`). None of this is forest/gold/cream. No variation is documented. This page has its own unrelated color system that belongs to a different brand ent
  4. 4. There are four sections: hero, features, use cases, footer. The studio floor is six. Add at minimum: how-it-works, pricing, and a proof/trust section.
  5. 5. No pricing section exists on this Tier 2 SMB tool page despite the JSON-LD declaring a $5-$199 price range. A visitor who wants to know what this costs has nowhere to go. Pricing transparency is non-negotiable at Tier 2.
  6. 6. No FAQ section. Required for Tier 2. At minimum answer: what counts as a "document," how is it different from Notion, what does the $5 tier actually get you.
  7. 7. The feature cards have no photography. Every card is a `#f9fafc` box with a heading and two lines of gray text. Compare revoscape.com, which uses real imagery inside every feature block to show the thing happening, not just describe it.
  8. 8. "Knowledge at the Speed of Thought" names no buyer, solves no problem, and could describe 40 different SaaS products. Rewrite the headline to name a specific person and the specific thing they stop losing (e.g., "The sales ops manager who s
  9. 9. There is no social proof section of any kind. Zero testimonials, no logo bar, no named result. A Tier 2 SMB buyer will not pay for an AI knowledge tool without seeing that someone else already did and it worked.
  10. 10. The visible body content is estimated under 400 words. The 1200-word floor exists because thin pages do not convert and cannot rank. Expand the features section, write a real "how it works" narrative, and give each use case actual depth.
  11. 11. All six feature cards use identical visual treatment: same `#f9fafc` background, same `#e2e8f0` border, same `12px` radius. This is the identical-gradient-card pattern the studio bans. Vary the layout, break at least two cards into a wider
  12. 12. The footer is a single centered line of copyright text in a dark bar. It links to nothing. Add at minimum: product sub-nav (pricing, faq, how it works), a company link back to wishdeal.com, and a contact or support path.
  13. 13. The use-case section (`usecase-list`) contains plain white boxes with one paragraph of copy each. No buyer title, no role label, no image. A prospect cannot see themselves in these cases because nothing in the box tells them it is for someo
  14. 14. The OG description is "Your organization's knowledge, finally searchable." This is a positioning tagline masquerading as a description. It tells a search engine and a link preview nothing about what the product does, who it is for, or why i
  15. 15. The body background `#f0f2f7` is a cold blue-gray. It is not warm. It creates a clinical feel that conflicts with the trust and ease this kind of product needs to communicate. Replace with the cream standard or a deliberate warm near-white.

bookkeeper-ai

Oct 18, 13:33 · 9KB · 15 demands shown
  1. 1. Replace the hero gradient with real photography. The hero background is `linear-gradient(135deg, #f4f7fb 0%, #e8f1f9 100%)` with no image. Every reference site (revoscape, proxybox, investwithdreams) leads with a real photo. A pale blue-gra
  2. 2. Add photography to each feature card. Feature cards contain only a green `h3` and a gray `p` - no visual anchors. The standard demands real photography in section feature blocks, not just the hero.
  3. 3. Make the nav sticky with `backdrop-filter: blur()`. The `.nav` rule has no `position: sticky`, no blur, and no transparency. Every polished reference site uses a sticky blurred nav. This one snaps to the top and disappears.
  4. 4. Remove the left accent bars from every use-case card. `.use-case { border-left: 4px solid #1db87a; }` is explicitly banned. That pattern appears across the entire use-case grid.
  5. 5. Document or replace the palette. Body uses `#f4f7fb` / `#e8f1f9` cool blue-grays with a `#1db87a` mint accent and `#0f1f3d` dark navy. This is not forest/gold/cream. No comment in the CSS acknowledges a deliberate deviation. Either own the
  6. 6. Add a data security section. This product handles client financial data. There is no mention of encryption, data isolation, or access controls anywhere on the page. A fractional CFO will not hand over client books to a product that says not
  7. 7. Add integration logos. "Accounting Automation" with no named connections to QuickBooks, Xero, Stripe, or bank feeds is an unverifiable claim. investwithdreams anchors its platform promises with partner logos. This page offers only prose.
  8. 8. Pick one buyer and rewrite the hero for them. "Accounting Automation for Fractional CFOs" and small-business-owner copy cannot coexist. A fractional CFO IS the accountant. A business owner HIRES one. They have different budgets, different f
  9. 9. Add a social proof section with real attribution. There are zero testimonials on the page. For a product that touches client financials, one named fractional CFO with a company name and a specific outcome is the minimum. Revoscape has three
  10. 10. Source every stat rendered by the `.stat` class. The standard prohibits big numbers without provenance. Every figure on this page needs a footnote, a methodology link, or removal.
  11. 11. Name the alternatives in the comparison table. A comparison table without named competitors reads as theater. Name QuickBooks, Bench, or manual bookkeeping staff with honest column headers. An anonymous "Traditional Bookkeeper" column is no
  12. 12. Kill `transform: scale(1.05)` on the featured pricing card. That CSS rule breaks mobile stacking and is a dated pattern. Use a visible label or border accent to signal the featured plan without physical scaling.
  13. 13. The closing CTA section is a wallpaper copy of the hero. Both use the identical gradient. A closing CTA should feel like a different emotional beat - earned trust, not visual déjà vu.
  14. 14. Add `/security` and `/faq` as real linked sub-pages. The standard requires actual sub-pages with real URLs. An inline FAQ div and a pricing section on the same scroll do not substitute for pages a prospect can bookmark or share with their o
  15. 15. Rewrite nav links to point to real sub-pages. `.nav-links` almost certainly contains `href="#features"` anchors that scroll within the same page. Replace with `/pricing`, `/faq`, `/security` so the page passes due-diligence scrutiny from a

company-brain

Oct 18, 12:46 · 10KB · 15 demands shown
  1. 1. Replace `Space Grotesk` with Fraunces for every header on the page. Why: Space Grotesk is an undocumented substitution that breaks the required Fraunces-serif-headers standard; the shell CSS already loads Fraunces and it goes completely unu
  2. 2. Delete the second `<link>` Google Fonts call loading `Space Grotesk` from the page `<head>`. Why: The shell already handles font loading; this adds a blocking render request for a non-compliant font, costing latency and producing the wrong
  3. 3. Replace the `#4f46e5` indigo CTA with a forest or gold color. Why: Indigo is a generic SaaS template color with no relationship to the studio palette; it reads as an uncleaned bootstrap default, not a deliberate choice.
  4. 4. Change the `#f0f2f7` body background to the cream palette standard. Why: Cold blue-gray is used on zero other factory builds and signals the page was assembled outside the design system entirely.
  5. 5. Put a real photograph in the hero section. Why: Every flagship in the reference set (proxybox, vendoriq, revoscape) uses real photography in the hero; the current flat gradient `#141c2e` to `#1a1f2e` communicates nothing about what Company
  6. 6. Add a real photograph or illustrated scene to at least two feature cards. Why: Studio standard requires real photography in section feature blocks, not `#f9fafc` text boxes; spearplus uses outcome cards with visuals and measurable numbers,
  7. 7. Add at minimum two more content sections to reach the six-section floor. Why: The page has hero, features, use cases, and footer, which is four sections against a mandatory minimum of six.
  8. 8. Add a pricing section that shows the three tiers declared in the JSON-LD (`$5` to `$199`). Why: Tier 2 SMB tools require pricing transparency on-page; the schema acknowledges three price points but no section exists, so the buyer has to cli
  9. 9. Add a FAQ section. Why: Tier 2 explicitly requires an FAQ; none is present anywhere on the page.
  10. 10. Audit body word count and confirm it reaches 1200 words. Why: Any page being actively sold requires 1200+ body words; the visible content (a headline, four feature cards, six use-case tiles) cannot plausibly reach that floor.
  11. 11. Rewrite the hero headline to name a specific buyer role, not an abstract concept. Why: "Knowledge at the Speed of Thought" tells no one anything; vendoriq leads with "Vendor Intelligence in Seconds, Not Weeks" naming a persona and a time co
  12. 12. Rewrite the hero subheadline to state one concrete outcome after adoption, not a complaint. Why: "Your organization's knowledge, finally searchable" describes a problem without promising a result; replace it with what changes for the operat
  13. 13. Give every use-case card a named persona and an active-verb outcome, not a category label. Why: Cards that read "Customer Support" or "Sales Enablement" describe job titles, not scenarios; spearplus names specific situations with measurable
  14. 14. Add a "how it works" section with numbered steps showing the integration and onboarding path. Why: There is no process narrative on the page; a Tier 2 buyer needs to understand the lift before committing, and the absence of steps makes the
  15. 15. Add at least one attributed proof point with a real name, role, and company. Why: Zero testimonials at any price point is disqualifying; the studio standard prohibits fake testimonials but requires honest ones, and the current page offers n

bookkeeper-ai

Oct 18, 11:49 · 11KB · 15 demands shown
  1. 1. The hero background is a flat CSS gradient. Replace it with a real photograph of a bookkeeper, accountant, or CFO at a desk. No gradient substitutes for a credible product photograph. Why: Studio standard, non-negotiable for any hero.
  2. 2. The nav has no `position: sticky`, no `backdrop-filter: blur()`, and no tinting. It is a plain white bar that disappears on scroll. Fix it. Why: Sticky tinted blur-nav is a non-negotiable studio standard; every flagship reference (revoscape
  3. 3. The color palette is navy blue (`#0f1f3d`) and light blue-gray (`#f4f7fb`). That is not the forest/green/gold/cream palette and there is no documented deviation. Either shift to the studio palette or commit a written variance with rationale
  4. 4. The use-case cards have `border-left: 4px solid #1db87a` on every single card. Left accent bars are explicitly prohibited. Remove them and find a different visual differentiator. Why: Studio standard explicitly bans left accent bars.
  5. 5. The feature section has no photographs, only gray-background cards with green headings. Add one real image per feature block or a single section-level photograph. Three cards with identical formatting and no photography is not a feature sec
  6. 6. The headline "Bookkeeper AI - Accounting Automation for Fractional CFOs" is a product category label, not a headline. Rewrite it as a direct outcome statement aimed at the fractional CFO. Example target: what they walk into a client meeting
  7. 7. The subtitle "Your books, done by morning" is in the JSON-LD but does not appear to be the visible hero headline. If the visible h1 is longer and more generic, cut it to that tagline. One sentence that lands for a 50-year-old CFO who has be
  8. 8. The stats block (`.stat` class elements) uses bare numbers in neon green. Every number on the page needs a source line or a methodology link. No numbers without provenance. Why: Studio standard on honest copy; investwithdreams links every c
  9. 9. The comparison table compares against what, exactly? "Traditional bookkeeping" is not a named competitor. Either name specific alternatives (QuickBooks Live, Bench, Pilot) or remove the table. An unnamed comparison is a claim without a targ
  10. 10. The pricing spans $5 to $199. Fractional CFOs bill clients at $100-$300 per hour. A $5 entry tier signals a consumer tool, not a professional one. Either raise the floor, rename the tiers to reflect professional use cases, or explain in cop
  11. 11. There are no named testimonials, no company logos, no headshots, no social proof of any kind visible in the HTML. Add at least two named practitioners (real name, firm, city) who use the product. Do not fabricate them. If they do not exist
  12. 12. The FAQ question text is styled `color: #1db87a` on a white background. Green question text reads as hyperlinks. Use dark text for questions and reserve green for CTAs only, or the user will try to click every FAQ question expecting navigat
  13. 13. The page has no sub-pages. A Tier 2 SMB tool requires at minimum a pricing page, an FAQ page, and an about page as distinct URLs. Inline FAQ sections do not count as sub-pages. Why: Studio standard; "real internal links, sub-pages exist."
  14. 14. The `cta-section` is another CSS gradient identical to the hero gradient. Two gradient backgrounds with the same colors is visual repetition that kills page rhythm. Replace the CTA section background with a dark photograph or a solid dark c
  15. 15. The footer is a single centered text block in dark navy. Add a four-column footer with product links, company links, legal links (privacy, terms), and a newsletter or contact option. The current footer is a dead end. Why: vendoriq and voice

bookkeeper-ai

Oct 18, 11:28 · 11KB · 15 demands shown
  1. 1. The hero has no real photograph. A CSS gradient is not a hero image. Replace it with a real photo of a CFO at a desk, a financial workspace, or actual accounting software on a screen. Why: Studio standard requires real photography in every
  2. 2. Use-case cards use `border-left: 4px solid #1db87a`. Left accent bars are explicitly prohibited by studio standards. Remove them and differentiate cards with icon treatment or a top-border + background contrast instead. Why: Left accent bar
  3. 3. The nav is a static white bar with a bottom border. It is not sticky and has no backdrop-filter blur. Add `position: sticky; top: 0; backdrop-filter: blur(12px); background: rgba(255,255,255,0.85)`. Why: Sticky tinted nav with blur is a non
  4. 4. The page palette (navy #0f1f3d, blue-gray #f4f7fb, bright green #1db87a) is not forest/gold/cream and no deviation is documented in the page. Either align to the palette or add a comment block at the top of the CSS naming this deviation and
  5. 5. The hero and the CTA section share the exact same gradient: `linear-gradient(135deg, #f4f7fb 0%, #e8f1f9 100%)`. Two sections cannot share a background without reading as a layout error. Give the CTA section a distinct treatment, a dark fil
  6. 6. The featured pricing card uses `transform: scale(1.05)`. This is a Themeforest template move from 2017. Replace it with a distinct visual treatment that earns the emphasis, a darker border, a badge, a contrasting fill. Why: The studio test
  7. 7. No social proof exists anywhere in the page structure. A Tier 2 SMB tool needs at minimum one named testimonial with real name, title, and company. Revoscape names theirs with photos. This page has none. Why: Anonymous or absent social proo
  8. 8. The `.stat` elements display green numbers but no source is visible anywhere on the page. Every asserted number must have a provenance note ("across X clients," "in our beta," "per 2024 survey") or be removed entirely. Why: Honest copy stan
  9. 9. No real photography exists in the features section or the use-case section. The standard requires real photography in section feature blocks, not only in the hero. Add at least one real image, an interface screenshot, a workflow diagram fro
  10. 10. All six feature cards are visually identical: same `#f9fafb` fill, same 1px gray border, same layout, no icons, no hierarchy. There is no focal point and no way to tell which feature is primary. Add a distinct icon or visual anchor to each
  11. 11. The hero headline (title tag reads "Accounting Automation for Fractional CFOs") is a product category description, not a promise. A fractional CFO does not buy "automation." Rewrite the h1 to name the actual outcome: hours saved, errors eli
  12. 12. The comparison table's losing column uses `color: #d97706`, which is amber/gold. Amber reads as caution or warmth, not defeat. Replace with `#9ca3af` neutral gray for competitor deficiencies so the visual hierarchy reads unambiguously. Why:
  13. 13. No product screenshot or interface preview exists on the page. A Tier 2 SMB buyer spending $99-199/month wants to see what they are purchasing before they hit the pricing section. Add at least one real interface screenshot above the fold or
  14. 14. The footer is a single dark bar with centered text and two links. Add columns: product links, company links (about, pricing, FAQ), and a legal line. Why: Investwithdreams and revoscape both structure their footers as navigational anchors; a
  15. 15. The page title targets fractional CFOs but the feature copy almost certainly speaks to any business owner. Fractional CFOs serve multiple clients simultaneously and need multi-entity support, client-facing reports, and hourly billing contex

bookkeeper-ai

Oct 18, 11:23 · 10KB · 15 demands shown
  1. 1. The `.nav` has no `position: sticky`, no `top: 0`, and no `backdrop-filter: blur()` - it scrolls away the moment a visitor moves, violating the sticky tinted nav standard every flagship in the reference set meets.
  2. 2. The hero background is `linear-gradient(135deg, #f4f7fb 0%, #e8f1f9 100%)` - a pale SaaS-blue CSS gradient with zero photography; proxybox.us and rootedmindsproject both open with real human or product imagery in the hero.
  3. 3. `.use-case { border-left: 4px solid #1db87a; }` puts a left accent bar on every use-case card - this is explicitly banned; remove the bar and differentiate cards through spacing and iconography instead.
  4. 4. The palette is dark-navy / bright-green / pale-blue-grey - not forest/gold/cream and nowhere in the file is a deliberate documented deviation; pick a palette and name it or align to the standard.
  5. 5. `#1db87a` is a Stripe-era neon SaaS green, not forest green - compare it to the favicon's own `#1f3a2e`; a bookkeeping product aimed at fractional CFOs needs a color that reads trust, not growth-hack.
  6. 6. Every feature card and use-case card is a plain bordered box with no photography and no illustration - revoscape and rootedmindsproject both use real imagery inside section feature blocks; swap at minimum one real photo per feature row.
  7. 7. The `.cta-section` repeats `linear-gradient(135deg, #f4f7fb 0%, #e8f1f9 100%)` verbatim from the hero - this is lazy section reuse; the closing CTA needs a visually distinct treatment that builds urgency, not déjà vu.
  8. 8. The JSON-LD schema declares `"lowPrice": "5"` - no fractional CFO service starts at $5; this undercuts the stated ICP instantly and signals a factory placeholder that was never sanity-checked.
  9. 9. The page title targets "Fractional CFOs" while the product is called "Bookkeeper AI" - fractional CFOs hire bookkeepers, they don't do bookkeeping; either change the ICP to "bookkeepers and small accounting firms" or change the product's va
  10. 10. There is no testimonial or social proof section class anywhere in the stylesheet - for a Tier 2 SMB tool handling someone's financial records, even two named quotes with a company name are non-negotiable; revoscape has a named photo bar, ro
  11. 11. `.faq-question { color: #1db87a; }` makes FAQ questions visually identical to links - users will click on them expecting navigation; FAQ questions should be dark body text, not link-colored.
  12. 12. The comparison table uses `color: #d97706` (amber) for X marks against competitors - amber reads as "partial credit" not "no"; use red or a neutral dark color so the competitive table actually lands a punch.
  13. 13. The `.pricing-card.featured { transform: scale(1.05); }` pattern is a 2019 SaaS template cliché - use a background-color shift, a badge, or a border treatment instead; the scale pop looks cheap next to any flagship reference.
  14. 14. The footer is a single centered paragraph on a dark-navy band with no column navigation - add at minimum three footer columns: product links, company links, and a trust line (privacy policy, terms, data handling); a one-line footer signals
  15. 15. There are two separate `<link>` tags loading Google Fonts - WD_SHELL_CSS_v1 already loads Fraunces + Inter + JetBrains Mono, then a second inline tag re-requests Fraunces + Inter; remove the duplicate to eliminate a redundant render-blockin

postgres-as-a-service-with-transparent-sharding-el

Oct 18, 10:39 · 9KB · 15 demands shown
  1. 1. The `<title>` tag names the product "Neki" but the JSON-LD schema names it "ShardLess" - pick one brand name and use it everywhere, or this reads as a half-finished page assembled by a script. Why: Basic brand integrity; proxybox.us does no
  2. 2. The hero is a CSS gradient (`#0e1726 → #1a2535`) with zero real photography - every hero requires a real image, not a dark gradient pretending to be atmosphere. Why: Non-negotiable studio standard; revoscape.com and investwithdreams.com bot
  3. 3. The nav uses `background: #fff` with no `backdrop-filter: blur()` - the sticky nav standard requires a tinted, blurred backdrop, not an opaque white bar that looks like a default stylesheet. Why: Studio standard; dailyunlock.us implements t
  4. 4. The entire palette is dark navy and electric blue (#2d6ef7) - this is not forest/gold/cream, and there is no documented variation in the page, so this is an undocumented deviation that will produce a disconnected multi-page experience. Why:
  5. 5. `.problem-section` uses `border-left: 4px solid #2d6ef7` - left accent bars are explicitly banned by the studio standards, full stop. Why: Listed as a forbidden pattern.
  6. 6. Every `.feature-card` has `border: 1px solid #e5e7eb` - identical borders on all cards is the exact pattern listed as banned. Why: Forbidden pattern; differentiate cards by content weight or visual hierarchy instead.
  7. 7. The CTA button is neon blue (#2d6ef7) - this is a neon accent color, not a palette-consistent call-to-action, and it clashes with the stated forest/gold/cream standard. Why: Studio standard on palette and no-neon-hero-numbers extends to pri
  8. 8. The hero headline is not visible in the provided HTML but the meta description ("Postgres at any scale, no sharding ceremony required") is developer-conference humor, not buyer copy - name the concrete outcome and the ICP: "The database for
  9. 9. The `<title>` tag has double spaces before and after the dash ("Neki - Postgres as a Service...") - this renders in browser tabs and search snippets and signals a generated page, not a built one. Why: Basic craft; every flagship reference
  10. 10. Fonts are loaded twice: once via the `WD_SHELL_CSS_v1` block and again inline in the `<head>` - this is a duplicate network request and signals the page was assembled by template injection without cleanup. Why: proxybox.us and spearplus.com
  11. 11. The background is `#fafbfc` - not cream, not a documented variation, just a default off-white that signals "I didn't think about this." Why: Studio palette standard; cream is `#faf7f0` or close to it, not a generic gray-white.
  12. 12. No testimonials, named users, or social proof are present in the visible HTML for a product asking engineers to trust it with their production database - Tier 2 requires honest social proof with a name and context, not anonymous bullets. Wh
  13. 13. The JSON-LD schema sets `"category": "general saas"` - this is meaningless for search engines and should be "Database" or "Infrastructure Software" to get schema relevance for the actual product category. Why: SEO craft; the schema is alrea
  14. 14. The nav-links are styled but their actual `href` targets are not present in the provided HTML - Tier 2 requires real sub-pages (pricing, docs, FAQ at minimum) not orphaned anchor tags. Why: Studio standard on real internal links; proxybox.u
  15. 15. The product's ICP is never named anywhere visible - "Postgres as a Service" could mean a solo developer, a fintech startup, or an e-commerce team, and each has a different reason to care about sharding. Name at least two concrete use-case s

bookkeeper-ai

Oct 18, 09:54 · 10KB · 15 demands shown
  1. 1. The nav has no `position: sticky`, no `backdrop-filter`, and no tinted background - it is a static white bar. Make it sticky with `backdrop-filter: blur(12px)` and a semi-transparent tint. Why: every flagship reference (dailyunlock, proxybo
  2. 2. The hero background is a flat CSS gradient (`linear-gradient(135deg, #f4f7fb, #e8f1f9`). There is no photo. Replace with a real photograph of a CFO or accountant reviewing a screen. Why: the studio standard is non-negotiable - real photogra
  3. 3. The feature cards are text-on-gray boxes with zero imagery. Add at least one real supporting photo anchoring the feature section. Why: "stock SVG icons are not a substitute" - neither is no visual at all.
  4. 4. Every use-case card uses `border-left: 4px solid #1db87a`. That is a prohibited pattern in the studio standards. Redesign as full-border cards or remove the accent entirely. Why: the standard explicitly bans left accent bars.
  5. 5. The palette (navy `#0f1f3d`, cool gray `#f4f7fb`, mint green `#1db87a`) is a generic SaaS-blue scheme with no documented rationale. Either align to forest/gold/cream or write a one-line variation note explaining why this palette was chosen
  6. 6. Pricing opens at $5/month for a product targeting fractional CFOs who bill at $150-300/hour. That floor price signals toy software to the exact buyer the title claims. Raise the entry tier to at least $49/month or remove it. Why: honest cop
  7. 7. The comparison table almost certainly benchmarks against "Traditional Bookkeeper" and "Spreadsheets." Name the real competitors - Bench, Pilot, Botkeeper, QuickBooks Live - or the table has no credibility. Why: revoscape names its competito
  8. 8. There is no testimonial section anywhere in the visible page structure. A Tier 2 SMB tool targeting CFOs needs at least two named, attributed proof points with company or use-case context. Add a social proof section or remove any implied cr
  9. 9. The CTA section at the bottom reuses the identical gradient as the hero. Give it a dark background, a photo background, or a contrasting solid color. Why: two sections with the same visual treatment at opposite ends of the page make the pag
  10. 10. The `.stat` class (green, bold, 1.1rem) suggests featured numbers somewhere in the body. Every number - "saves X hours," "clients served," "accuracy rate" - must have a source note or be removed. Why: honest copy standard bans big numbers w
  11. 11. The footer is a single centered text block. There are no footer columns, no legal links, no sub-page navigation, no company description. Build a two or three column footer with real links. Why: the real-internal-links standard requires sub-
  12. 12. The product shows no screenshot of the actual output - no dashboard, no reconciled report, no categorized transaction view. A bookkeeping AI that never shows what "books done by morning" looks like is asking the buyer to take a $149/month l
  13. 13. Feature card `h3` elements are styled `color: #1db87a` - the same green used for CTAs, links, checkmarks, and pricing figures. Green on everything destroys hierarchy and makes feature titles look like labels. Use dark text (`#0f1f3d`) for `
  14. 14. The page title claims fractional CFOs as the ICP, but fractional CFOs manage books for multiple client companies simultaneously. The copy needs to explicitly address multi-client use: separate workspaces, client-level reporting, white-label
  15. 15. The featured pricing card uses `transform: scale(1.05)` which is a broken pattern on mobile - it clips against its container and creates horizontal scroll. Replace the scale with a border highlight and a "Most Popular" badge. Why: mobile-fi

bookkeeper-ai

Oct 18, 09:43 · 10KB · 15 demands shown
  1. 1. Replace the hero background with a real photograph. Why: the hero is a two-tone CSS gradient; every flagship page (vendoriq, revoscape, investwithdreams) leads with a real image, and a financial automation tool needs visual credibility befo
  2. 2. Make the nav sticky with `position: sticky; top: 0; backdrop-filter: blur(16px); background: rgba(255,255,255,0.85)`. Why: the studio standard is non-negotiable and the current flat white bar disappears on scroll.
  3. 3. Remove the `border-left: 4px solid #1db87a` from every use-case card. Why: identical left accent bars are explicitly banned; differentiate with typography or a small icon instead.
  4. 4. Document or abandon the cold navy/teal/blue-gray palette. Why: the studio standard is forest/gold/cream and this deviation is undocumented; the page reads "generic SaaS" not a trusted accounting product.
  5. 5. Change the pricing number color from `#1db87a` to the dark navy `#0f1f3d`. Why: neon accent-colored pricing numbers are explicitly banned; reserve green for the "per month" label only.
  6. 6. Replace the CTA section gradient with a dark full-bleed background (forest or navy) with white text. Why: the bottom repeats the same `linear-gradient` as the hero, giving the page a recycled-wrapper feel; investwithdreams closes with visua
  7. 7. Name the comparison table columns with real alternatives (e.g. "Traditional Bookkeeper," "QuickBooks + manual entry," "In-house accountant"). Why: unnamed columns make the comparison table meaningless and look like placeholder content.
  8. 8. Add at least one named testimonial with a job title and company before the footer. Why: a financial automation product asking for trust has zero social proof; even one real quote is a conversion floor.
  9. 9. Add one distinct visual element (icon or screenshot) per feature card. Why: the current cards are gray boxes with a green H3 and gray text; proxybox.us makes each feature instantly scannable with a small icon anchor.
  10. 10. Swap the H1 to "Your books, done by morning" and demote "Accounting Automation for Fractional CFOs" to a subtitle. Why: the schema description already chose the human headline; the current H1 is a category description, not a value propositi
  11. 11. Replace the featured pricing card's `transform: scale(1.05)` with a dark background fill and a "Most Popular" badge. Why: CSS scale breaks mobile grid alignment and is a pattern from 2016; every polished pricing section in this studio uses
  12. 12. Add a logo row naming at least three integrations (QuickBooks, Xero, Gusto). Why: a bookkeeping AI that does not name its connectors makes every fractional CFO ask "does it work with my stack"; vendoriq has a full integrations page; a logo
  13. 13. Change the FAQ question color from `#1db87a` to dark navy. Why: bright green question labels read as UI decoration, not content hierarchy; they should be readable Fraunces headers, not accent labels.
  14. 14. Change the body background from `#f4f7fb` (cold blue-gray) to a warm near-white or cream. Why: cold blue backgrounds read as developer tools; accounting products signal trust through warmth; the studio palette specifies cream for this reaso
  15. 15. Add one credibility signal (a named stat with source, a media mention, or an authority logo) directly below the hero CTA buttons. Why: investwithdreams and revoscape both show a trust bar before the features section; the hero currently offe

bookkeeper-ai

Oct 18, 09:06 · 9KB · 15 demands shown
  1. 1. Every heading (`h1`, `h2`, `h3`, `.logo`, `.feature h3`, `.faq-item h3`) declares `font-family: 'Plus Jakarta Sans'` which is never loaded - Fraunces IS loaded and never used; swap every `Plus Jakarta Sans` reference to `Fraunces` immediate
  2. 2. The hero is a flat navy-to-navy CSS gradient with no photography - VendorIQ puts a real Unsplash photo under its hero with a dark overlay; add a full-bleed photo of a freelancer's desk or accountant workspace behind this hero.
  3. 3. Feature icons are single emoji characters inside green rounded squares - these are not visual content; replace them with real product screenshots or contextual photography in each feature card, as proxybox.us does in its feature blocks.
  4. 4. The sticky nav uses a solid `background: #0f1f3d` with no `backdrop-filter` property anywhere in the stylesheet - add `backdrop-filter: blur(12px)` and a semi-transparent fill; a solid opaque band is not the glass nav the standard requires.
  5. 5. The body background is `#eef2f7`, a clinical blue-gray used in medical-records software - switch to `#faf7f0` (warm cream) to signal reassurance rather than cold enterprise tech; this matters more for a product handling someone's finances.
  6. 6. The entire palette (navy, teal-green, blue-gray) contains zero gold or earth tone - document the deliberate variation from forest/gold/cream in the page comments, or introduce a warm accent; undocumented palette deviations are not variation
  7. 7. The trust section shows four large green stat numbers with no citation, methodology link, or case-study reference - remove every number without a source or add a footnote per number; the standard is no big numbers without provenance.
  8. 8. There are zero testimonials on this page - revoscape.com shows three named-photo testimonials with a venue logo bar; a tool that handles someone's financial records and compliance needs at least one named human with a job title and business
  9. 9. The page has five content sections (hero, features, trust stats, FAQ, pricing) and a footer - the floor is six; add a "How It Works" three-step section (connect accounts, AI categorizes, review and export) which is the minimum trust-builder
  10. 10. The H1 is the product name "Bookkeeper AI," not a benefit - the OG description already contains the stronger line ("Your books, done by morning"); move that to H1 and demote the product name to an eyebrow or logo.
  11. 11. The hero subhead ("Automated transaction categorization, compliance-ready reports, and real-time cash flow visibility") is a feature dump in three nouns - rewrite it as a single sentence in second-person addressing the freelancer's actual f
  12. 12. The meta description simultaneously targets "freelancers and agencies" - these are two distinct buyers with different compliance needs and price sensitivity; commit to one ICP on this page and let the other have a separate URL.
  13. 13. There is no integrations or "works with" row - a bookkeeping tool with no QuickBooks, Xero, Stripe, or bank-connection logos shown has no credibility; trydesk.org demonstrates a clean logo bar that handles this in one section.
  14. 14. The pricing section contains copy and a CTA button but no actual price - "talk to us" pricing on a freelancer-facing tool is a conversion wall; show at least one concrete price tier even if additional tiers require contact.
  15. 15. No "who this is for" anchor exists anywhere on the page - a visitor who isn't sure if this fits their situation has nothing to self-select against; add a single visual block naming the exact target ("Made for: independent contractors, consu

company-brain

Oct 18, 08:49 · 9KB · 15 demands shown
  1. 1. Replace `Space Grotesk` headers with `Fraunces` serif. Why: The studio standard is Fraunces/Inter and this page loads Space Grotesk in a second `<link>` tag that overrides the shell's already-loaded Fraunces, wasting a font load and breakin
  2. 2. Put a real photograph behind the hero. Why: The hero is a pure `linear-gradient(135deg, #141c2e 0%, #1a1f2e 100%)` with zero imagery. VendorIQ, the closest reference, drops a full-bleed Unsplash photo behind its hero on day one.
  3. 3. Swap `#4f46e5` indigo out of the CTA button and every accent. Why: The studio palette is forest/gold/cream. Indigo is not a documented variation and nothing in the page explains the divergence.
  4. 4. Change the body background from `#f0f2f7` cold blue-gray to cream. Why: The forest/gold/cream palette requires it, and the current value reads as a generic bootstrap app shell, not a product page.
  5. 5. Add at minimum two more sections to reach the six-section floor. The visible structure is: hero, features, use cases, footer. That is four. Why: Studio standard is 6+ sections; Tier 2 (SMB tool) requires enough depth to handle a skeptical b
  6. 6. Add a dedicated pricing section on this page, not buried in a JSON-LD blob. Why: The schema already advertises three tiers from $5 to $199. Tier 2 explicitly demands pricing transparency. The buyer has no idea what they are paying without l
  7. 7. Add an FAQ section with at least five questions specific to CompanyBrain's use case. Why: Tier 2 non-negotiable. No FAQ exists anywhere on this page.
  8. 8. Rewrite the hero headline away from "Knowledge at the Speed of Thought." Why: That phrase has appeared on IBM ads, Microsoft Copilot decks, and a dozen Notion competitors. Name the specific pain the product solves in plain English.
  9. 9. Rewrite the meta description "Your organization's knowledge, finally searchable." as a complete sentence that names who this is for and what they stop losing. Why: Sentence fragments read as placeholder copy; Confluence and Guru say the sam
  10. 10. Give each feature card a distinct visual treatment, not identical `background: #f9fafc; border: 1px solid #e2e8f0` on every card. Why: Studio standard forbids identical gradient borders on cards; flat identical borders are the same failure
  11. 11. Add at least one real photograph or authentic screenshot inside a feature block. Why: Studio standard requires real photography in section feature blocks. Styled-text cards alone do not pass the stranger test.
  12. 12. Add a social proof section with attributed names, roles, or company types. Why: There is no testimonial, logo bar, or usage stat on the page. Even a single honest named quote with context beats the current void.
  13. 13. Any numbers used in the copy must have a provenance note inline or in a footnote. Why: Studio standard is honest copy; numbers without sourcing read as invented.
  14. 14. Remove the second `<link>` tag loading Space Grotesk. Why: The shell already loads Fraunces, Inter, and JetBrains Mono in the first CSS block; duplicating a font request for a font that should not be used anyway is double waste.
  15. 15. Bring the footer above the bare-minimum four-line treatment. It currently has no links, no product-level navigation, no legal text, and no contact path. Why: Even TryDesk (the lightest reference site) has a navigable footer that links to su

appointment-setter-ai

Oct 18, 07:37 · 9KB · 15 demands shown
  1. 1. The hero section uses a CSS gradient (`linear-gradient(135deg, #f7f4f1 0%, #f0ebe5 100%)`) with no photograph. Add a real photo of a sales rep booking a meeting or a calendar interface in action. Every flagship from proxybox to revoscape op
  2. 2. Remove `border-left: 3px solid #1c1c1c` from every `.benefit-card`. Left accent bars are explicitly banned by studio standard, no exceptions.
  3. 3. The primary CTA buttons are black (`#1c1c1c`). There is zero gold anywhere on the page. Either use gold as the action color or document this palette departure in writing.
  4. 4. Forest green (`#1f3a2e`) appears nowhere in the palette. This is not a documented variation. Add it to the nav, CTAs, or section backgrounds or file a variance.
  5. 5. The `.benefit-stat` elements display large numbers with no sourced provenance. Source every stat or delete it. "40% more meetings" without a footnote is dishonest copy per studio standard.
  6. 6. The feature cards are text-only with no images. Studio standard requires real photography in section feature blocks. Add a real screenshot or photograph to at least three of the feature cards.
  7. 7. There is no Pricing section. Tier 2 SMB tools require pricing transparency. VendorIQ shows tiers and a "Get Early Access" path. Add a pricing section with at least one visible price anchor or a "starts at" number.
  8. 8. There is no FAQ section. Tier 2 standard. Write at minimum five questions your buyer actually asks: CRM compatibility, setup time, what happens when a lead doesn't pick up, data privacy, and contract length.
  9. 9. There is no social proof section. Add two to three honest named testimonials with company and role, or a logo bar of named users. Revoscape carries three named photos with venue logos. This page has none.
  10. 10. The hero tagline reads like a feature list ("Convert more leads, free your reps from calendar work"). Rewrite it around the cost of the problem: the lead that went cold because no one followed up fast enough.
  11. 11. The solution section uses `content: '>'` as list bullets. Replace with a real checkmark or remove the bullets entirely. Angle brackets as decorative glyphs read as developer placeholder copy.
  12. 12. The page has six sections, which is the floor, but contains no Pricing, FAQ, or social proof section. You are three sections short of a credible Tier 2 page.
  13. 13. No sub-pages exist or are linked in the footer. Add links to at minimum: pricing, FAQ, and about. Proxybox and VendorIQ both carry multi-page structures with real internal link graphs.
  14. 14. The meta description ("Convert more leads, free your reps from calendar work") contains no number, no ICP, and no differentiation. Rewrite with a specific outcome and named buyer: "Sales teams using Appointment Setter AI book X more meeting
  15. 15. The page title is "Appointment Setter AI | Automated Sales Scheduling." It names neither the ICP nor the brand. Rewrite: "Appointment Setter AI for SDR Teams | [Brand Name]" so a stranger clicking a link knows immediately if this is for the

bookkeeper-ai

Oct 18, 06:06 · 10KB · 15 demands shown
  1. 1. Every heading (`h1`, `h2`, `h3`, `.logo`) specifies `'Plus Jakarta Sans'` but that font is never imported -- every heading on the page is rendering in system fallback sans-serif. Import Fraunces and apply it to all headings per the studio s
  2. 2. The hero headline "Precise. Plain. Reassuring." is three adjectives, not a benefit. A freelancer at 11pm before tax season does not know what this product does from those words. Rewrite to lead with the outcome: what does their life look li
  3. 3. The body background is `#eef2f7` and borders are `#d4e4f2` -- a cool medical blue-gray that appears in zero reference flagships. Replace with forest/gold/cream (`#faf7f0` body, `#1f3a2e` forest nav, gold accents) or document why this palett
  4. 4. The nav is `background: #0f1f3d` solid with no `backdrop-filter`. Add `backdrop-filter: blur(16px)` and drop the background to semi-transparent so it reads tinted over content, not painted over it. See dailyunlock.us nav for the exact patte
  5. 5. The four green stat cards have zero provenance -- no source, no date, no methodology. Remove them or replace with a metric you can actually document, the way proxybox.us names its "1,200+ residential IPs" with clear context.
  6. 6. Every feature block uses an emoji inside an identical 48x48 green square. This is a stock icon substituting for real imagery. Swap in product screenshots or in-context photography as feature illustrations, the same way revoscape.com uses ve
  7. 7. There is no photograph of a human being anywhere on this page. Add a real photo of the ICP (a freelancer reviewing financials, a two-person agency team) in the hero or a split-image section. A bookkeeping product sells on trust and three bo
  8. 8. The pricing section shows no dollar amounts -- it ends with a secondary CTA button and a vague paragraph. This is a Tier 2 SMB tool; pricing transparency is required. Show at least one named tier with a price.
  9. 9. The page has five content sections (hero, features, stats, FAQ, pricing). The minimum is six. The `explainer.mp4` asset exists at `/factory/builds/bookkeeper-ai/explainer.mp4` and is unused. Surface it as a "See It Work" section between fea
  10. 10. There are no testimonials from named humans. The stats section uses numbers not people. Add one attributed quote minimum -- full name, business type, specific result -- the way revoscape carries three named photos with venue logos in their
  11. 11. On mobile, `nav { display: none }` kills the entire navigation with no hamburger replacement. The page has zero mobile navigation.
  12. 12. The hero body text reads "Automated transaction categorization, compliance-ready reports, and real-time cash flow visibility" -- that is a feature list compressed into a sentence, not a value proposition. Tell the customer what pain goes aw
  13. 13. The sub-pages `about`, `pricing`, `how-it-works`, `faq`, `integrations`, and `vs` all exist in the build directory but none are linked from the main nav. A stranger opening this URL has no path to any of them.
  14. 14. The footer has a single link. Wire up at minimum FAQ, Pricing, About, and How It Works in the footer nav -- every reference flagship from proxybox to dailyunlock has a multi-column footer with internal links.
  15. 15. The `vs` sub-page exists at `/bookkeeper-ai/vs/index.html` but there is no surface on the homepage pointing to it, not even a one-liner. Name the alternative (QuickBooks, Wave, a human bookkeeper) explicitly on the homepage and link to the

bookkeeper-ai

Oct 18, 05:33 · 12KB · 15 demands shown
  1. 1. The body font is `Plus Jakarta Sans`, not Inter -- swap it to Inter or document the deviation in the brand file. Why: the studio standard is Fraunces + Inter; an undocumented override means every build drifts independently with no coherent
  2. 2. The sticky nav has no `backdrop-filter: blur()` and no tint -- add it now. Why: the nav is plain white with a `border-bottom`, indistinguishable from a 2018 Bootstrap starter kit; every flagship reference site (proxybox, investwithdreams) u
  3. 3. Problem cards carry a `border-left: 4px solid #1db87a` accent bar -- remove them entirely. Why: left accent bars are explicitly banned by studio standards; their presence here means the builder ignored the antipatterns list.
  4. 4. The page palette is navy/mint-green/cold-blue-gray -- there is no gold, no cream, no forest tone anywhere. Why: the studio standard is forest/gold/cream, or a documented variation; this palette belongs to a generic fintech SaaS template, no
  5. 5. The body background is `#f4f7f9` (cold blue-gray), not a warm cream -- replace with a cream base (`#faf7f0` range) consistent with the studio palette. Why: the cold-gray background signals "tech dashboard" to a small business owner who need
  6. 6. The hero image element exists but has no confirmed real photograph of a small business owner -- it must be a real photo, not a UI screenshot or generated graphic. Why: studio standard requires real photography in every hero without exceptio
  7. 7. There is no photography anywhere in the solution/feature block cards -- text-only white cards with a box-shadow is not a feature presentation, it is a placeholder. Why: revoscape.com uses environmental photography throughout to anchor abstr
  8. 8. There is no testimonials section in the page structure -- add at least two named testimonials with business type and a concrete quantified outcome. Why: at Tier 2, named social proof is required; the page currently has zero human voices bey
  9. 9. All pricing cards share the identical hover treatment (`border-color: #1db87a` on every tier) -- give the recommended tier a visually distinct featured state that is visible without hover. Why: identical gradient/color borders on all cards
  10. 10. The final CTA section uses `linear-gradient(135deg, #0f1f3d, #1a2e5c)` -- replace it with a solid brand color or a photographic section. Why: gradient wash backgrounds are the "orb background" equivalent for dark sections and are banned; da
  11. 11. There is no data trust or security statement anywhere on the page -- add one plain-language sentence about how bank connections work (read-only, encrypted, no write access). Why: a small business owner connecting their bank account will aba
  12. 12. The headline "Automate Your Books, Keep Your Sanity" uses accountant vocabulary ("Books") aimed at the buyer's internal monologue as an accountant, not as a plumber or florist -- rewrite it for the person who calls it "my finances" or "my a
  13. 13. The page has no standalone sub-pages -- create at minimum a `/pricing` and `/faq` page with real URLs. Why: a prospect sharing this link with their accountant cannot deep-link to pricing; an accordion FAQ section is not a discoverable page.
  14. 14. The nav has no links to pricing or FAQ anchors or sub-pages -- a mobile visitor has no way to jump directly to cost without scrolling the entire page. Why: the sticky nav exists to aid navigation, and it currently leads nowhere except the h
  15. 15. The logo color in-page (`#0f1f3d` dark navy) contradicts the favicon (`#1f3a2e` dark forest green) -- unify the brand color for the logotype. Why: the brand identity is incoherent before the visitor reads a single word; the favicon promises

bookkeeper-ai

Oct 18, 03:48 · 11KB · 15 demands shown
  1. 1. Replace Plus Jakarta Sans with Inter as the body font. The page declares `font-family: 'Plus Jakarta Sans', sans-serif` on the body element while simultaneously loading Inter via factory.css, creating a competing font stack with no document
  2. 2. Add `backdrop-filter: blur()` and a tint to the nav. The header is `background: white` with a plain border-bottom; there is no blur, no tint, no glass feel. Why: sticky tinted nav with backdrop-filter is a hard studio requirement, and every
  3. 3. Remove the `border-left: 4px solid #1db87a` from every `.problem-card`. Three cards, identical left bars, same green. Why: left accent bars are explicitly prohibited by studio antipatterns.
  4. 4. Document or replace the navy-green-gray palette. The studio standard is Forest/gold/cream; this page uses #0f1f3d/#1db87a/#f4f7f9 (tech startup SaaS blue-green) with no deviation documented anywhere in the build. Why: undocumented palette d
  5. 5. Put a real photograph in the hero, not a software-dashboard screenshot. The `.hero-image` class implies a UI mockup will land there; revoscape uses a full-bleed venue photo, rootedmindsproject uses a real person in context. A screenshot of
  6. 6. Remove the identical hover treatment across all pricing cards. Every `.pricing-card:hover` resolves to the same `border-color: #1db87a` plus the same green glow shadow, which is exactly the "identical gradient borders on cards" prohibited p
  7. 7. Add a real social proof section with at least one named, verifiable person. The page flows problem → solution → how-it-works → pricing → FAQ → CTA with zero testimonials, zero logos, zero named users. Why: proxybox, spearplus, and revoscape
  8. 8. Put a photograph or real visual in the CTA final section. The `cta-final` is a pure `linear-gradient(135deg, #0f1f3d, #1a2e5c)` dark gradient block with no image, no face, no credibility anchor. Why: dark gradient-only CTA sections are a te
  9. 9. Add at least Pricing and FAQ to the visible nav links. The nav currently shows only a logo and a single CTA button; there are no internal navigation links to sections or sub-pages. Why: real internal links are a studio standard, and a Tier
  10. 10. Remove the duplicate Fraunces import. The page imports Fraunces twice: once via the factory.css shell link (`opsz,wght@9..144,400;...`) and again inline with a stripped `wght@600;700` call, doubling the font network request. Why: basic buil
  11. 11. Remove #1db87a from `.price` text. The price numbers are displayed in the same neon green as every button and accent on the page, making them feel like a UI highlight rather than a serious pricing signal. Why: "no neon hero numbers" standar
  12. 12. Name the ICP in the hero subheadline. "Automate your books, keep your sanity" targets no one; the prospect reading it does not know if this is for them or someone else. Revoscape's hero names the venue operator. Spearplus names the team sca
  13. 13. Give the solution cards a real visual differentiator. All six `.solution-card` elements have an h3 and a paragraph, no icon, no illustration, no photograph. They read as a bulleted list in card clothing. Why: proxybox and spearplus both pai
  14. 14. Audit the full page copy for em dashes before shipping. The HTML excerpt is CSS only; the body copy has not been checked. Em dashes are prohibited. Why: studio standard, zero exceptions.
  15. 15. Add an About page or a "Who made this" footer credit with a real name and provenance. There is no sub-page and no indication of who built or stands behind Bookkeeper AI. Why: real internal sub-pages are a studio standard, and anonymous SMB

bookkeeper-ai

Oct 18, 03:03 · 10KB · 15 demands shown
  1. 1. Replace `Plus Jakarta Sans` body font with Inter across the entire stylesheet. The studio standard is Fraunces headers + Inter body, documented in `WD_SHELL_CSS_v1` already loaded on this page - you then loaded a competing font that overrid
  2. 2. Scrap the navy/emerald palette (`#0f1f3d` / `#1db87a` / `#f4f7f9`) and replace with forest/gold/cream. The body background reads like a cold SaaS dashboard; a bookkeeping product handling real money needs the warm, grounded palette that sig
  3. 3. Add `backdrop-filter: blur(12px)` and a semi-transparent tint to the sticky nav. The current `background: white` nav is a flat wall; every flagship in the reference set uses blur - proxybox.us, dailyunlock.us, spearplus.com all do it correc
  4. 4. Remove every `border-left: 4px solid` accent bar from `.problem-card`. Left accent bars are explicitly banned. Replace with an icon or a soft top-edge highlight if visual separation is needed.
  5. 5. Put a real photograph in the hero. A person at a desk reviewing a laptop, a bookkeeper at work, a small business owner looking relieved - not a product screenshot floating on a white card. Revoscape's hero is a real environment photo; this
  6. 6. Add a real photograph to at least one feature section. SVG-style icons and step numbers do not substitute for photography in feature blocks.
  7. 7. Kill the identical `border-color: #1db87a` hover state applied uniformly to all pricing cards. Every card lighting up with the same green glow is exactly "identical gradient borders on cards." Give the recommended plan a permanently elevate
  8. 8. Remove the `linear-gradient(135deg, #0f1f3d, #1a2e5c)` CTA section. A navy gradient closing block is the definition of the gradient backgrounds this studio rejects. Replace with a solid forest section or a real photo background at low opaci
  9. 9. Add a named social-proof section with at least two real testimonials: name, business type, and a face. Tier 2 requires this. The page has zero visible social proof. Trydesk.org and proxybox.us both carry named proof blocks. Anonymous or abs
  10. 10. Add a trust/security callout specifically for financial data. One sentence about how transaction data is handled - not SOC 2 (that's Tier 4) but something honest: "Your bank connection is read-only. We never move money." A bookkeeping AI wi
  11. 11. Fraunces is loaded twice - once in `WD_SHELL_CSS_v1` and once in a redundant `<link>` tag three lines later. Remove the duplicate load; it adds a render-blocking request with zero benefit.
  12. 12. The FAQ answers have no visible expand/collapse behavior in the CSS - `cursor: pointer` on `.faq-question` but no JS handler or toggle class shown. Verify the FAQ is actually interactive; if it is not, every answer is collapsed with no way
  13. 13. Write a concrete ICP into the hero headline. "Automate Your Books, Keep Your Sanity" is SaaS-generic. Rewrite to name who this is for: a freelancer, a 5-person service business, a restaurant owner. Spearplus.com's hero names its audience in
  14. 14. Add a logo bar above or below the hero CTA. Even six invented company name placeholders are better than nothing. For a Tier 2 tool, a 3-5 client logo strip signals that real businesses are using this. Revoscape carries a venue logo bar for
  15. 15. The pricing section has placeholder-style card names and no visible annual/monthly toggle. If there are real pricing tiers, show the billing cadence options. If not, label one tier "Coming Soon" or "Waitlist" rather than presenting a grid o

bookkeeper-ai

Oct 18, 02:11 · 10KB · 15 demands shown
  1. 1. The body font is `Plus Jakarta Sans`, not Inter - strip the inline font override and use the Inter that's already loaded via WD_SHELL_CSS_v1, or the page is running two conflicting font stacks for no reason. Why: studio standard is Fraunces
  2. 2. The palette is dark navy + neon lime + blue-grey (`#0f1f3d`, `#1db87a`, `#f4f7f9`) - this is a generic fintech SaaS template, not the studio's forest/gold/cream standard; replace the entire color system. Why: every flagship from investwithd
  3. 3. The nav is `background: white` with a 1px border and zero `backdrop-filter` - it is not sticky-tinted with blur; add `backdrop-filter: blur(16px)` and a semi-transparent tinted background. Why: studio non-negotiable, and every reference sit
  4. 4. The `.problem-card` elements have `border-left: 4px solid #1db87a` - left accent bars are explicitly banned; remove them from every card on the page. Why: studio standard, flagged as a prohibited pattern.
  5. 5. The hero has a generic `.hero-image` slot - confirm there is a real photograph of a person (a small business owner, an accountant at a desk) in this space, not a UI screenshot, a dashboard mockup, or an illustration; stock SVG is not accept
  6. 6. The solution section has six text-only cards with no photography - each feature block needs a real supporting image or photograph, not just a headline and two sentences. Why: studio standard demands real photography in section feature block
  7. 7. There is no social proof section anywhere visible in the page structure - no named testimonials, no client logos, no usage numbers with provenance; add at least three named testimonials with name, title, and company, or remove the testimoni
  8. 8. The pricing section lives on the main page but there is no `/pricing` sub-page - for a Tier 2 SMB tool, pricing must exist as a real navigable page with a persistent URL a prospect can bookmark and share. Why: studio standard requires real
  9. 9. The nav links almost certainly all resolve to `#section-anchor` on one page - there is no `/about`, `/faq`, `/pricing` in the file structure; build them or the nav is a cosmetic lie. Why: studio standard, "Real internal links. Sub-pages exi
  10. 10. The `#1db87a` green is neon lime and reads like a payments startup accent color - a bookkeeping service needs a color that signals trust and precision, not growth-hacking; mute it to a sage or forest green in the 40-60% saturation range. Wh
  11. 11. The `cta-final` block is `linear-gradient(135deg, #0f1f3d 0%, #1a2e5c 100%)` - two shades of the same dark navy is a gradient cliche with no warmth and no brand personality; replace it with a real brand color treatment. Why: dailyunlock and
  12. 12. There are no integration logos anywhere - a bookkeeper AI product's primary trust signal is "it connects to QuickBooks, Xero, and your bank"; put a row of integration badges directly below the hero or in the features section. Why: proxybox
  13. 13. The "Automate Your Books, Keep Your Sanity" headline is a consumer-anxiety hook, not a positioning statement - rewrite it to say exactly what the product does and who it is for in one concrete sentence, the way trydesk's headline names the
  14. 14. The `.problem-card` section and `.solution-card` section are structurally identical white-card grids with the same padding, radius, and shadow - they look like the same template repeated twice with different section titles; differentiate th
  15. 15. The page title metadata says "Bookkeeper AI" but the logo div reads `Bookkeeper AI` in plain Fraunces with no mark or wordmark treatment - build a real logo or wordmark lockup consistent with what spearplus and proxybox do with their nav id