Proof of work · not a padded résumé
I’m Meet Shah, the builder behind FastPress Labs. I ship zero-dependency developer tools and launch pages that work for humans, search engines and AI agents. Everything below links to public code or a dated report.
Remote-friendly · timezone and work-authorization details on request · no cookies, no analytics
01 · Selected work
Three projects, each with public source and a verifiable result. No client logos I cannot name, no numbers I cannot source.
Grade a launch page before the internet does.
A zero-dependency Node CLI that runs 53 checks across conversion, trust, technical, SEO, social, accessibility and AI-agent readiness. I wrote the checks, weighted scoring, terminal/HTML/Markdown/JSON reports, SVG badge, GitHub Action, MCP server and agent skill.
A launch partner page that had to earn trust.
Rebuilt a one-page growth-partner site with no build step: new positioning, real proof instead of invented testimonials, accessible forms, SEO/OG/JSON-LD, and free-form audit and collaboration intake. The before and after are both published.
Open-source launch tools for people who ship.
Set up the org, profile README, community health files, issue templates, docs and release process. The rule is simple: no fake stars, no fake case studies, no dark patterns. If a result is published, it has a date and a source.
02 · What I actually do
I am most useful at the seam between product, code and distribution: make the thing, make it legible, then make it findable.
Node.js, vanilla JavaScript, semantic HTML and responsive CSS. Zero build steps where a build step would only add risk.
Evidence: LaunchGrade sourceCLIs, GitHub Actions, MCP servers, tests with node:test and documentation a stranger can follow without a call.
Technical SEO, Open Graph, accessibility, security headers and AI-agent readiness: robots, sitemaps, llms.txt, AGENTS.md.
READMEs, launch copy, legal pages, dark UI systems, SVG marks and social cards. Clear beats clever when someone is deciding whether to trust you.
Evidence: community docs03 · How I work
A working audit beats a roadmap for an audit platform. Then improve the thing people already use.
If there is no source, it does not go on the page. Dated snapshots are honest; rounded-up claims are not.
The README is part of the product. If a stranger cannot run it, it is not finished.
Source, tests, reports, changelog. Trust is easier when the work is inspectable.
04 · Availability
I am open to conversations about freelance launch audits and build sprints, open-source collaboration, and full-time product engineering, founding engineer or developer-experience roles.
Remote-friendly. Timezone and work-authorization details on request. No recruiter spam, please: one specific role or project is enough.
Good fit
05 · Questions
Yes. I am open to full-time product engineering, founding engineer and developer-experience roles, as well as freelance launch work and open-source collaboration.
This page does not guess. Ask and you will get the real city, timezone and work-authorization details.
One paragraph with the role or project, the company, the timeline and what good looks like. A link is welcome. No deck is required.
Freelance work is scoped and priced in writing before it starts. No surprise retainers.
Yes. Every project on this page links to public source, a passing test suite or a dated audit report.
06 · Contact
Tell me the role, the project or the problem. A sentence about what “good” looks like is enough. I read everything and reply like a human.
No list. No sequence. No analytics on this page.
Still reading?
If you need proof before a call, start with the code. If you need a person, send the brief.