A self-hosted workflow for agencies and freelancers

Give your next offer a better start, without hours of manual page research.

Bring a first review into your offer preparation. Spend less time gathering page details, make a more focused discovery call, and shape proposals around the goals the client confirms.

Ask about the source license Check the technical fit

Source package, version 0.3.16-prelaunch. Report requests are processed immediately, then delivered as PDF email attachments. The package requires protected SMTP settings, Arranz Gnome, Python, Node.js, Lighthouse, and Chrome. It uses no database or background worker.

Protect your proposal margin

Keep unpaid prep proportionate
to the opportunity.

A quick first look can help you decide whether a prospect merits deeper analysis. Save detailed recommendations for paid work, then price a scope around what the client confirms.

PREPARE →
⌕

Cut repetitive prep

Give your team a faster way to collect first-page evidence during proposal prep.

DISCOVER →
◉

Ask about the right things

Take page-specific questions into discovery and learn which points matter to the client.

PROPOSE ✓
✳

Scope with context

Frame a first step with clear assumptions, deliverables, and exclusions before you estimate implementation.

A focused first review

Bring a stronger starting point
to your next client conversation.

The report gives your team a page-specific starting point for discovery, with observed page evidence, the host’s public robots.txt status and same-host sitemap links, and one mobile Lighthouse lab run. Take the findings into the conversation, confirm what connects to the client’s goals, and use their answers to shape the offer.

Review the hosting requirements
WHAT YOUR TEAM CAN USE

Evidence for a better scoped first offer

✳
✓
Page-specific observationsSee the source evidence behind each automated finding
✓
Questions for discoveryCheck the client’s goal before you treat a technical signal as a priority
✓
A conditional validation scopeDiscuss a bounded first project when the client confirms there is an opportunity
✓
Keep the proposal focusedUse page evidence to guide discovery, then scope around the client’s confirmed priority
✓
Clear limits and lab contextSee what one page and one Lighthouse run can establish

Designed for a technical team to operate

Self-host the workflow.
Know what running it involves.

This is a manually provisioned source package, not a hosted subscription or one-click installer. Your team operates the web host, local AI service, SMTP settings, and security configuration.

Runtime requirements

  • Supported x64 Windows Server with IIS FastCGI and HTTPS
  • PHP 8.4 or later with process execution enabled
  • Python 3.11 or later, Node.js 22.19 through 24.x, and Google Chrome
  • pnpm 11.25.0 to install the pinned Lighthouse and Puppeteer dependencies

Provision and operate

  • Keep the public document root at www/, outside application and private settings
  • Set protected environment values for PHP FastCGI and its CLI child process
  • Set the IIS request timeout above four minutes for the synchronous report flow
  • Run the bundled diagnostic and verify a report reaches the submitted email address

Know the product boundaries

  • One public page and a bounded robots.txt check, with no sitewide crawl or Google Search Console connection
  • One mobile-emulated Lighthouse lab run, not real-user field Core Web Vitals
  • No ranking, traffic, conversion, revenue, or ROI forecasts
  • The completed report arrives as a PDF attachment at the submitted business email address. The application does not show report contents in the browser or send marketing email.
  • The stated source-license fee does not include support, updates, hosting, or installation
  • The current source package is still in prelaunch acceptance and IIS FastCGI has not been exercised here

Data and analytics: the application processes each report temporarily, sends it as a PDF email attachment, and removes temporary files after the delivery attempt. It does not retain report data. The package ships with Matomo disabled, so it sends no analytics requests and shows no analytics-cookie modal by default. To enable it, configure an HTTPS endpoint and site ID in www/assets/matomo-config.js, update the Content Security Policy and privacy and cookie notices, and confirm how that Matomo instance handles visitor data.

The deployment guide covers the direct report flow, protected SMTP settings, local Gnome configuration, and the bundled diagnostic. There is no automatic updater. Test release changes in your own environment before production.

✳

Start with fit and license terms

Keep your prep focused.
Keep the client conversation yours.

Tell us about your deployment environment and the way your team prepares offers. We can discuss the source-license agreement and whether the current package fits your setup.

Discuss the source license Release candidate: 0.3.8-prelaunch, acceptance and target-host checks remain