Companion to the Founder Dossier

Strengths and weaknesses, stated plainly.

The dossier makes the case for what's been built. This page makes the case for how I actually operate — including where the real risk sits, not just where the wins are. Same rule as everything else on this site: no figure or claim that wouldn't survive being checked.

Prepared: July 14, 2026  ·  ← Back to the founder dossier

The one number that matters most here

One month. Near-zero budget. Perfect scores, verified.

30 days
Starting from four brand-new domains and no existing infrastructure, I taught myself, tooled up, and shipped verified 100/100/100/100 mobile PageSpeed scores — Performance, Accessibility, Best Practices, and SEO — across every property I operate, on a budget best measured in domain registrations and my own time. No agency, no paid course, no team. That's the whole claim in this section, and it's the one every reviewer can re-check themselves in under a minute per domain at pagespeed.web.dev.

That timeline is the argument for everything below: it's evidence of how fast I actually learn a discipline from zero to a verifiable, repeatable standard — not a one-time trick on a single page, but a methodology now applied across eleven industry blueprints, six competitor platforms, and every client site I build.

What I bring

Strengths

Speed of mastery

Zero to verified expert, fast, on a real constraint

The PageSpeed result above isn't a one-off. The same one-month runway also produced a public incident log, a WCAG accessibility discipline good enough to pass manual screen-reader review, and a working technical-SEO standard — each learned to a publishable, defensible standard rather than a passable one.

Radical transparency as a working method

I publish the mistakes, not just the wins

107 incidents are logged publicly, each with the standing rule it produced. Two finished audits were pulled from my own portfolio for not meeting my bar. This isn't a marketing angle — it's how I actually catch and fix my own errors, and it's directly checkable.

Full-stack solo execution

One person, agency-scale output

Design, development, copywriting, technical SEO, accessibility auditing, and cold outreach — all handled personally, at a pace and consistency that normally requires a small team. That's a direct answer to "can this person actually ship," not a claim about it.

Mission alignment under real constraint

Built a free tool with a reason to stay free

USA Benefits Navigator carries zero monetization by deliberate choice — no ads, no tracking, no donation asks — because I built it from firsthand experience needing that exact kind of information. It would be easy to monetize; I've chosen not to, on principle, and kept that choice even while pre-revenue.

Systemized, not one-off, quality control

Every bug becomes a permanent rule

Findings don't just get patched — they get converted into a standing rule applied retroactively across every property, not just the page where the bug was found. That's the mechanism that let one person hold agency-level consistency across four domains and dozens of pages.

What I'm still solving for

Weaknesses

None of this is hidden in the fine print, and none of it should surprise anyone who read the dossier carefully. Naming it directly is the same discipline as the incident log.

Bus factor

I am currently the only point of failure

No employees, no contractors, no second engineer reviewing my own code before it ships. The incident log is how I catch mistakes after the fact; there's no peer review catching them before. This is the direct tradeoff of moving this fast alone.

Pre-revenue by design

The build-first model front-loads all the cost onto me

Clients review finished, working sites before paying — which means every hour of build time is unpaid until a client says yes. Two new pay-upfront products (Ledger, PerfectScoresWebsite) are a deliberate step toward earlier cash flow, but self-serve checkout still routes through a waitlist email until Stripe activates August 14, 2026.

Unproven at enterprise scale

Cold outreach to Fortune 500 CEOs is sent, not yet closed

I've sent direct, evidence-backed outreach to CEOs at major platforms and enterprises with real audit findings attached. None of that has converted into a signed enterprise contract yet. I'd rather state that plainly than let a reader assume otherwise.

Young track record

Every domain here is under 30 days old

The velocity is real and verifiable, but it's also recent. There isn't yet a multi-year history of this standard holding up under scale, staff turnover (there is none to turn over), or a much larger client base. That evidence will only come with time.

Generalist by necessity

Breadth over narrow specialization

Covering design, engineering, SEO, accessibility, copy, and business development personally is a strength for output, but it means less depth in any single narrow specialty than a dedicated hire in that one area would have. I'm explicit about this rather than overselling any one skill as deeper than it is.

For employers specifically

Removing the risk from your side

I'd rather be paid for the work, and the track record above is the case for why. But I understand that hiring a solo, fast-moving generalist is itself a judgment call for an employer, and I don't expect anyone to take that on faith.

If it helps get to a decision faster: I'm open to a one-month working trial at no cost — you see the actual output, the actual pace, and the actual communication style firsthand, with no financial risk on your end, before anything is formalized. A paid arrangement from day one is preferred and the outcome I'm working toward, but I'd rather remove every reason to say "not sure yet" than protect my own downside on this.