Developer tools decision
Maximeb
A technical user can recreate the public website and product pages quickly, but cannot reproduce the studio's PR reach, media relationships, or any proprietary growth services that provide the product's real value.
Visit website↗Not priced
No pricing page we fetched carried a figure, so there is nothing to compare against. The build side is still real.
$20one-off12 h to build
$0/mo2 h/mo upkeep
No published price to break even against.
No open-source build does this yet
Nothing published replaces this one, so a replacement starts from an empty file. Here is what it would have to cover.
What a replacement has to do
- Serve a small marketing/studio portfolio site that lists products, links, and basic analytics.
What it still won’t have
- Existing brand recognition and PR relationships (500+ outlet coverage)
- Any proprietary distribution or growth services sold by the studio (MediaBoost)
- Non-public operational knowledge and studio processes
What remains hard
- Brand trust
PR coverage on 500+ top media outlets.
First-year cost
No published price
Maximeb does not publish a price we could read, so there is nothing to compare against. What building costs is below.
Money you would actually spend
Time you would spend
—
What you would spend
What we assumed
The verdict above measures whether you could build it. This one is only about money.
Runnable build prompt
Build a static portfolio site in Next.js (React) deployed to Vercel that lists a small studio and three product pages. In scope: a homepage, per-product pages (title, description, external link), an admin-editable content flow using MDX files or a headless CMS (e.g., Sanity/Contentful), a contact form wired to SendGrid (or SMTP) with serverless function, automated CI/CD deploys, and pageview analytics via Plausible. Out of scope: reproducing the studio's PR distribution service, proprietary marketing/backlink delivery, and any macOS native apps. Include error handling for broken links and form failures, basic unit/integration tests for build pipeline, and a README with deploy steps.
How we checked
How the score was reached
- Partly verdict base52
- Evidence score52
The base comes from the verdict. Everything under it is a check that either happened or did not, and each one is a fact frozen in this record rather than a judgement made at render time - so the same evidence always produces the same number.
How scoring works →Integrity checks
What held up, and what did not.
