
Let’s be honest: modern billing departments aren’t trying to resolve your queries. They don’t have to. Why would they hire humans to negotiate with you when they can unleash tireless, infinite loops of automated, algorithmically generated final-adjustment notices, post-relocation “ghost charges,” and predatory demands for gym memberships that have outlived your interest in fitness by several geological eras?
They know that eventually, you will suffer from a very natural, very human condition: bureaucratic exhaustion.
The asymmetric warfare of the modern economy relies on this exact friction. They have automated, multi-tiered siege machines of billing software. You have a blank email draft, an unmonitored noreply@ address, and a vague, fading sense that what they are doing is probably illegal. Most of us eventually pay up just to buy back our peace of mind from the collection agencies.
After my own recent soul-crushing relocation—where I found myself buried under a flurry of ghost charges and aggressive demand letters for accounts I had painstakingly closed months prior—I spent countless, irreplaceable hours of my life hunting down Escalation Contacts and verifying physical addresses.
I decided I was done playing defense. That is why I built Countermark at my latest hackathon. It is automation backfire for the weary.
TRY IT OUT:
Here is the illustration of the asymmetric billing war I survived, and what we’re trying to claw back with Countermark.
What is Countermark?
Countermark takes hours of stressful, manual detective work and turns it into a structured, ready-to-send dispute draft in about two minutes. Think of it as a tactical shield to meet their billing spear.
- Notice Ingestion via Paste or Upload: Drop raw dispute text, paste frantic emails, or upload PDF billing notices directly. It extracts reference numbers, disputed amounts, and timeline data with no hesitation.
- Smart Recipient Detection with Confidence Badges: It trawls the notice and looks at domain heuristics to isolate the most likely destination for your pushback. Since companies hate transparency, it stamps a candid, honest Confidence Badge (High, Inferred, None) alongside cautionary warnings when the target looks like an automated role-based graveyard.
- Curated Consumer & Regulatory Links: It pairs your dispute with category-mapped, statutory consumer support pages, ombudsman bodies, and dispute resolution schemes, so you know exactly which higher power to summon.
- Dual Dispatch Workflow: Hit
mailto:to launch a structured, plain-language dispute draft in your default email client, or copy plain text in one click to insert directly into secure consumer portals.
The Blueprint
Countermark is built on Next.js, leveraging Google Gemini to handle multi-modal document extraction and draft generation.
We feed Gemini raw text or uploaded PDF notices. It cuts through unpredictable digital layers and multi-column layouts to extract contact endpoints and build an assertive, fact-based dispute draft. By integrating standard mailto: encoding alongside clipboard fallbacks, we solved the age-old problem of getting this payload safely to where it hurts them.
The Technical Graveyard (Challenges We Ran Into)
- Gemini Latency and 503 Spikes: Throwing giant, chaotic PDF documents at Gemini during peak API traffic occasionally led to the dreaded 30–90 second processing lag or upstream 503 errors. We spent a good deal of time engineering robust loading states, UX reassurance, and retry cycles.
- Messy PDF Parsing: PDF format should be illegal. Multi-column billing statements, scanned receipts, and broken digital text layers made clean parsing feels like decoding dead languages. It forced us to become meticulous with schema definitions and parsing constraints.
mailto:URI Limits: When your dispute is heavily itemized, it can push against the hard length limit of traditional browser and email client protocols. The dual handoff (mailto vs. markdown/plain text) became our fallback to bypass this digital bottleneck.- Managing Token Burn: Balancing API spending and prompt prototyping on unpredictable file sizes required strict guardrails to prevent an ironic, massive cloud billing crisis of our own.
Accomplishments that we’re proud of
- An Honest, Grounded UX: No AI magic-talk here. Just honest confidence badges, realistic status pills, and direct warning labels that keep the human completely in control.
- Defeating the Blank-Page Paralysis: Going from a threatening billing statement to a professional, cold, defensive dispute letter takes seconds, giving stressed people an instant handhold.
- Slick Fallbacks: Bypassing client-side URI encoding limits so you can confidently grab clean text to slam into portals when desktop mail fails.

What We Learned (or, Survival Guide)
Planning schema and data boundaries on day one saves countless architectural refactors. Pair with your AI as a dedicated sounding board for edge cases, and most importantly: when users are stressed, honesty beats promise. Rotating copywriting and progress indicators build more trust than over-promising automation.
What’s Next?
We want to build local dispute histories to help track deadliness right from your own privacy-conscious storage. We are actively expanding the directory of independent ombudsman escalation targets, sector-specific presets (formal, cancellation, debt proof), and batch ingestion.
Until then—don’t let the automated bill machines wear you down. Try it out, check the code, and start fighting back.



















