Skip to main content

Operating limit · no more than two concurrent engagements

Rodolf Boctor.

Rodolf is the founder and delivery lead of ThynkQ. He spent his earlier career at Meta and Sanofi, and now runs a senior engineering studio built on a simple contract: fixed scope, fixed price, documented handoff, and a system your team owns when he leaves.

No sales layer. You work directly with the people scoping, building, and handing over the product.

Rodolf Boctor, Founder, engineering lead at ThynkQ
Founder, engineering leadLinkedInGitLab

Operating standard

What the studio holds to.

2

Concurrent engagement focus

1

Accountable delivery owner

Proof

Evidence before claims

Handoff

Clear next owner

Track record

What has shipped, in order.

Mar 2026

ThynkQ startsNow

PL Maps for PowerLiens: a client-owned provider-search interface documented as a public work example. The case record names the evidence and its limits.

PL Maps, the case this timeline opens with. Read the case study.

Feb 2026

ProTeach co-founded

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

2025

Production engineering

Prior work across production software, release workflows, and human-review paths. Client-specific detail stays private when it is not appropriate to publish.

2022-24

Engineering practice

A working practice built around clear scope, testable releases, and an accountable handoff instead of a detached delivery process.

Stack

What the work is built with.

Languages

TypeScript · JavaScript · Python · SQL

Frontend

Next.js · React 19 · Motion · Tailwind CSS · WebSockets

Backend

Node.js · PostgreSQL · Drizzle ORM · REST APIs

AI / ML

Multi-LLM routing · LangChain · RAG · Streaming

Infrastructure

Vercel · AWS · Docker · GitLab CI · CI/CD

Payments

Stripe · Subscriptions · Webhooks · Billing systems

Delivery model

One lead. Every layer.

We turn hard product decisions into software your team owns. Scope, architecture, and quality decisions stay with the founder. Client communication does too. Specialists support specific tasks under that review layer.

  • We own the full stack: frontend, backend, database, auth, payments, AI, infrastructure, deployment. The engineer who designs the architecture is the one who monitors it in production.
  • Monitoring, error handling, CI/CD, and security ship as defaults, not afterthoughts, on every engagement.
  • You work directly with Rodolf, who scopes, designs, and builds it. Project management keeps the schedule; it does not stand between you and the person writing the code.

Founder-led with specialist support.

Best fitLaunch in the next quarter with one decision owner available weekly.

Not fitLowest-cost shopping, undefined ownership, or broad discovery without a timeline.

The next decision

Software your team owns. A clear next decision.

We accept no more than two concurrent engagements so scope, architecture, and handoff stay directly accountable. Start with the project details to confirm timing and scope.