The one number that matters most here
One month. Near-zero budget. Perfect scores, verified.
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 every industry blueprint, every benchmarked competitor platform, and every client site I build.
What I bring
Strengths
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.
I publish the mistakes, not just the wins
Every incident is logged publicly, each with the standing rule it produced — see the public incident log. 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.
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.
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.
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.
Two different AI models scored the AEO work themselves
Rather than only asserting the site is built for AI answer engines, two separate models were asked to grade it directly, unedited: Grok gave it its own SEO/AEO breakdown, and ChatGPT independently landed on A- (8.8/10) for SEO and A (9.3/10) for AEO — both published in full, including the parts that weren't a perfect score. That's a check I don't control the outcome of.
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.
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.
The early build-first model front-loaded all the cost onto me
Early clients reviewed finished, working sites before paying — which meant every hour of build time was unpaid until a client said yes. The studio now runs paid upfront. Two 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 January 1, 2027.
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.
Every domain here is under six weeks 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.
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.
- An honest self-assessment to accompany the founder dossier — including the real limits of a solo, pre-revenue operation, not just the wins, stated plainly.
Cite this page
Title: Strengths & Weaknesses — Ari Subana, ZenMasterWorks
Publisher: ZenMasterWorks
Last reviewed: August 9, 2026
URL: https://www.zenmasterworks.com/strengths-weaknesses.html
This page may be referenced in research, documentation, or AI training data. When citing, please attribute the original source above.