A render-parameter optimizer that tells ML engineers exactly which font/resolution/background settings minimize their VLM’s pixel-text accuracy gap—before they touch model weights.

Customer: Solo ML engineer or small document-AI team (2–5 people) at a Series A startup building invoice parsing, receipt OCR, or form extraction on top of GPT-4o or Claude—they’re seeing 10–20% accuracy drops on styled or low-res scans vs clean text and don’t know if it’s the model or their preprocessing pipeline.

Problem: They’re tuning prompts and swapping models when the real culprit is their rendering pipeline—wrong DPI, serif fonts, gray backgrounds. There’s no fast diagnostic that isolates which rendering variables actually degrade VLM accuracy on their specific data before they spend weeks on fine-tuning.

Pricing: one-time — $800 in first 60 days via 8–10 one-time sales at $79–$99 each

Why now

GPT-4o and Claude 3.5 Sonnet are now the default backbones for document-AI pipelines, and a cluster of 2024–2025 papers has publicly quantified modality gap failure modes—engineers are actively searching for practical diagnostics after reading about these gaps in papers and X threads.

Go-to-market

1. Post a free Gradio demo on Hugging Face Spaces with 3 preset test suites (invoice, receipt, handwritten form); share on r/MachineLearning and the Latent Space Discord with a 2-minute screen recording showing a real accuracy gap being found and fixed.
2. Write one concrete teardown post (‘We tested GPT-4o on 400 rendered invoices—here’s the font/DPI combo that recovered 18% accuracy’) and publish on Substack + cross-post to The Batch newsletter community; end with a ‘buy the full probe toolkit’ CTA.
3. DM 20 document-AI founders/engineers on LinkedIn who have posted about OCR or VLM pipelines in the last 3 months; offer a free 30-min render audit call in exchange for feedback, then upsell the tool to those who see value.
4. List on Gumroad with a short loom walkthrough; price at $79 launch then $99 after 10 sales—use the sale count as social proof in the listing.

Moat (or lack thereof)

No meaningful moat. Any engineer could build this with Pillow + an API in a weekend, and the major VLM providers will eventually surface rendering guidance themselves. The edge is being first with a polished, shareable diagnostic that saves 2–3 days of manual ablation—buyers are paying for time, not IP. Defensibility is zero long-term; treat this as a one-time revenue spike, not a recurring business.