Skip to main content

Find out what is wrong with your build before you pay to fix it.

A one-week, fixed $7,500 Build Readiness Audit. The fee is credited toward a Launch Build or Product Build signed within 60 days. For founders and teams whose AI-built or agency-built product now has to hold up.

  • PL Maps Client delivery
  • mcp-scan Public tool + source
  • ProTeach Predates ThynkQ

Who builds it

Rodolf Boctor, Founder, engineering lead at ThynkQ

Rodolf Boctor

Founder, engineering lead

We accept no more than two concurrent engagements.

Recent delivery

PL Maps product interface: find-a-provider search panel beside a live map of the LA basin dense with clustered provider pins, running on synthetic records

PL Maps product UI. Synthetic demo records only. The client owns the production system.

PowerLiens · Shipped across four weeks

PL Maps

Replaced PowerLiens' MapQuest dependency with map infrastructure, provider routing, and a search tool PowerLiens owns outright.

Read the case study
ProTeach status page from the public product surface

ProTeach public marketing site capture. No signed-in user data in frame.

Founder-built · Predates ThynkQ

ProTeach

Homeschool platform our founder co-founded and built: teacher-guided lessons, gamified learning, and parent progress tracking. Predates ThynkQ. Not a client engagement.

See the build

Due diligence · Security

Client evidence

Work you can inspect.

The PowerLiens engagement is stated at the level its public case study already supports, and every line carries the source you can open.

Client deliveryLive in production

PowerLiens

PL Maps: replaced a paid MapQuest dependency with map infrastructure PowerLiens owns, shipped in 4 weeks

Public case study and an interface demo on invented records. The production system is behind the client's login. Built for PowerLiens; PowerLiens owns the system, its data, and its roadmap.

  • NDA-protectedOne NDA-safe healthcare AI engagement: intake, scheduling, and operationsWork index
  • PublicOpen source security tooling for MCP infrastructuremcp-scan source

Two free tools, before any conversation about a build.

The mcp-scan check surface: a package name field, the Check package button, and the three checks it runs before a server is added to a client config.The mcp-scan check surface: a package name field, the Check package button, and the three checks it runs before a server is added to a client config.

rag-eval-toolkit

LLM-as-judge RAG evaluation. Python, MIT licensed, on PyPI.

$ pip install rag-eval-toolkit

13 metrics, 12 of them judge prompts in files you can read and edit.

Into the build

  1. The delivery lead stays on the build through the production handoff. The full studio roster is public.

    See the studio
  2. One command scans an MCP server configuration before you trust it.

    mcp-scan overview
  3. PL Maps replaced a licensed map dependency with a search tool PowerLiens owns outright.

    See the week-by-week delivery
  4. Each proof row links to a public source you can open.

    See the proof
  • A cold dark hall. The studio astronaut drifts past the camera, tilted, with empty void under its boots and one blue seam of light far below it.

    The delivery lead stays on the build through the production handoff. The full studio roster is public.

    See the studio
  • The camera closes on the mcp-scan check screen: the package field, the Check package button and the Try one chips, filling the frame.

    One command scans an MCP server configuration before you trust it.

    mcp-scan overview
  • A network map of providers hangs low in a corridor of vertical light, a filter card at its left and lit pins across the map.

    PL Maps replaced a licensed map dependency with a search tool PowerLiens owns outright.

    See the week-by-week delivery
  • The flight comes to rest on the proof surface: a lit page panel alone on a calm wall, one floor line running under it.

    Each proof row links to a public source you can open.

    See the proof

A single continuous camera move through a cold dark hall, built from the studio's own captures. The camera passes the studio astronaut drifting through the void, closes on the mcp-scan check screen, crosses a network map of providers in a corridor of vertical light, and comes to rest on the proof page alone on a calm wall. Depth and light do the reveal: nothing in the hall is animated, scroll only moves time, and the four surfaces are readable without the motion.

No black-box build period.

Scope, proof, and handoff stay legible through the work. The mode changes. The standard does not.

ScopeBuild Readiness Audit, scope

Included

  • A ranked list: what is broken, what it costs to fix, and in what order
  • Plain notes on the big technical choices, with the options we weighed
  • Security and performance problems found, with what to fix first
  • A short summary you can share with partners or investors

Not included

  • Implementation work, this audit diagnoses and sequences it
  • Multi-week delivery or production deployment
  • A stand-in for Launch Build or Product Build when launch is already urgent
Commitmcp-scan 414f87f, 2026-09-05
src/utils/repo-hint.ts@@ -50,6 +50,20 @@ function looksLikeFilePath(candidate: string): boolean {+// `npx --package=<pkg> <bin>` (and the space-separated / `-p` variants) runs+// a different binary than the package that provides it, so the first+// non-flag arg is the bin name, not the package. Look for an explicit+// --package/-p first and only fall back to "first bare arg" when there isn't one.+function packageArgFrom(args: string[]): string | undefined {+  for (let i = 0; i < args.length; i++) {+    const arg = args[i];+    if (arg === '--package' || arg === '-p') return args[i + 1];+    if (arg.startsWith('--package=')) return arg.slice('--package='.length);+    if (arg.startsWith('-p=')) return arg.slice('-p='.length);+  }+  return args.find(a => !a.startsWith('-'));+}@@ -62,7 +76,7 @@ export function findBadgeablePackage(report: ScanReport): string | undefined {-    const pkgArg = result.connection?.args?.find(a => !a.startsWith('-'));+    const pkgArg = packageArgFrom(result.connection?.args ?? []);
Handoffmcp-scan README

Badge

Publish an MCP server yourself? Get a public badge for its README:

npx mcp-scan badge <your-npm-package-name>

Prints a ready-to-paste Markdown snippet linking to a hosted scan report at thynkq.com. The command itself makes no network calls and needs no account, but the badge image is served by thynkq.com and loads whenever someone views the README.

Read the delivery standard

What arrives with a Launch Build.

4 weeks at $30,000. Weekly milestone cadence across 4 weeks with proof checkpoints.

  • Written scope with acceptance criteria by milestone
  • Weekly proof updates with shipped deltas and next decisions
  • Production deployment checklist and launch report
  • Handoff docs covering architecture, operations, and support path

At handoff

Production codebase, CI/CD, launch docs, and a 30-day support window

See a real oneRead the sample Build Readiness Audit report

50/50 on everything up to $59,999. Three milestones (40/30/30) on $60,000+ engagements. The deposit is fully refundable if you cancel before kickoff begins, and non-refundable once kickoff begins. No work starts before the deposit clears. Unusual integration scope is quoted after a free scoping call.

FAQ

Before you book

What should I book first?

Start with the free fit call unless you already know you need paid working time. The free call is the default entry point.

Do you offer short-term plans?

Yes. Rescue Sprint is the 2-week option for one blocked workflow, and Launch Build is the 4-week fixed-price option for one defined product area. Both start with the free call.

What happens on the free call?

We pressure-test the blocker, the budget band, the timeline, and the right starting point. If there is no fit, we will say so directly.

What if I am not sure of my budget yet?

Book anyway. The call pressure-tests the blocker, not the budget. If the budget is genuinely not in range, we will say so directly and we stop there. No pressure to proceed.

How fast can work start after that?

Usually within a few days once scope is aligned. Bigger builds depend on current capacity and how much of the project is already clear.

We finish what we start.

We reply within two business days with a fit decision and a clear next step.