10 bounded engagements
Each service has a published price, delivery window, scope, and limitation. No rankings, revenue, security, or conversion outcome is promised.
Public web propertyStart here
A rigorous, bounded review of the design, trust, SEO/AEO, performance, and conversion evidence that matters first.
One public website: the homepage plus up to four key journey pages.
- Executive verdict and five highest-priority actions
- Desktop and mobile design, UX, and trust review
- Offer, copy, and conversion-path review
- Technical SEO, AEO/GEO, structured-data, and social-preview checks
- Performance and accessibility spot checks
- Evidence tied to exact pages and reproducible observations
- A practical 14-day improvement plan
- Self-contained HTML report plus SHA-256-verified Markdown source
Design, SEO, AEO/GEO, agent readiness, conversion, performance, and accessibility reviewed as one growth system.
One public website and up to 15 representative pages.
- Executive scorecard and prioritized findings
- Visual design, UX, mobile, and trust review
- Technical and on-page SEO review
- Answer-engine and generative-engine discoverability review
- Conversion, offer, copy, and funnel review
- Performance, accessibility, and structured-data checks
- Cross-page evidence matrix with reproducible checks
- A practical 30-day implementation plan
A conversion-focused homepage designed, written, built, and browser-tested from observable evidence instead of generic templates.
One responsive homepage for an existing public brand or product website, delivered as self-contained HTML, CSS, and JavaScript or an equivalent implementation-ready component in the target's observable frontend stack.
- Audience, offer, conversion-path, trust-signal, and constraint brief
- Homepage information architecture and conversion-focused copy
- High-fidelity responsive visual design tailored to the brand
- Production-ready homepage source in the private delivery
- Accurate technical SEO, AEO, and structured-data recommendations
- Desktop and mobile browser QA with accessibility and performance checks
- Implementation notes, verification evidence, and launch checklist
A senior-engineering review focused on defects, security boundaries, maintainability, tests, and release risk.
One public GitHub repository up to 50,000 source lines. Larger or private repositories require a scoped quote.
- Findings ordered by severity with file and line references
- Correctness, security, dependency, and data-boundary review
- Architecture and maintainability assessment
- Test, CI, and release-gap analysis
- Prioritized remediation plan
- Plain-language executive summary
Can an AI agent discover, understand, trust, buy from, and successfully use your service?
One public agent-facing service, API, MCP server, or paid endpoint.
- Agent discovery and crawlability review
- llms.txt, schema, OpenAPI, MCP, and capability-contract checks
- Offer, checkout, x402, and payment-proof review where present
- Buyer-journey test from first request through fulfillment
- Trust, provenance, privacy, and failure-mode findings
- Prioritized agent-readiness remediation plan
A focused review of CI, publishing, provenance, secrets, and rollback readiness before the next release hurts.
One public GitHub repository and its checked-in CI/release configuration.
- GitHub Actions and release-flow findings
- Permissions, secrets, and token-boundary review
- Dependency and package-publishing risk review
- Versioning, provenance, rollback, and recovery assessment
- Prioritized fixes with verification steps
An evidence-first source review of webhook verification, duplicate handling, retries and processing boundaries.
One public GitHub repository, one webhook integration and up to three event-processing paths, capped at 10,000 relevant source lines. Read-only review of checked-in code, tests and configuration.
- Delivery-to-processing flow map for the scoped integration
- Signature verification and acceptance-boundary findings with file and line references
- Duplicate handling, idempotency, ordering and retry review
- Queue failure, recovery and observability gap analysis
- Prioritized fixes with focused regression-test recommendations
- Self-contained HTML report plus SHA-256-verified Markdown source
Written scope approval required
A bounded, explicitly authorized review of exposed services, login flows and application access boundaries.
One owner-authorized SaaS application and up to five agreed endpoints or flows. Prefer staging and owner-provided test accounts; public exposure observations are limited to an exact approved target allowlist.
- Scope and authorization receipt with exact targets, permitted methods and stop conditions
- Bounded exposed database, storage and admin-interface observations without accessing customer records
- Login, password-reset and session-handling findings within agreed test flows
- Authorization and cross-account isolation checks using approved test accounts only
- Severity-ranked evidence, safe reproduction steps and prioritized remediation recommendations
- Self-contained HTML report plus SHA-256-verified Markdown source
One reproducible repository issue, a tested patch, and payment only on verified delivery.
One public GitHub repository pinned to an agreed commit and one small reproducible bug, broken test or CI issue. Supported stack, reproduction, acceptance criteria and execution requirements are agreed before work is accepted.
- Agreed scope and acceptance test with a preserved failing baseline
- A focused patch, or pull request only with explicit maintainer authorization
- A regression test and before/after evidence for the agreed acceptance criteria
- Relevant test results, disclosed baseline failures, base commit and patch summary
- One in-scope correction round requested within seven days of delivery
Static microsite / scope approval first
A focused one-page site for a developer tool, open-source project or small service.
One responsive static page with up to five sections, built from client-supplied approved copy, brand assets and one primary call to action. Source is handed off for a client-owned repository; no private repository access is needed.
- Agreed one-page brief, section outline and primary call to action
- Responsive HTML, CSS and minimal JavaScript source
- Page title, description, canonical URL and social-preview metadata using approved facts
- Desktop and mobile browser checks, keyboard checks and a launch checklist
- Source handoff and deployment instructions for client-owned hosting
- One consolidated in-scope revision requested within seven days of delivery
