RODGERS INTELLIGENCE GROUP · DENVER, COLORADOFree intake Test Kit →
RIGRODGERS INTELLIGENCE
Menu
An illustrative photograph of a designer desk with wireframe sketches
Custom apps

THE MISSING TOOL, SCOPED AND HANDED OVER.

The workflow is missing a tool: an internal application, a client-facing app, or a decision and routing tool.

The One-Workflow Review, and everything else on this site, is scoped and priced after a short conversation.

Book a free 30-minute readiness conversationSend a briefGet the free Test Kit
Discuss this
Who it is for

THE WORKFLOW NEEDS A TOOL THAT DOES NOT EXIST YET.

Owners and operations leads whose workflow is missing one tool. One useful user journey with permissions, tests and handover: quoted after a short brief, with acceptance tests agreed before the build starts.

Send a brief
What you get

WHAT THE BUILD DELIVERS.

One scoped toolOne scoped internal application, client-facing app, or decision and routing tool.Send a brief →
Acceptance tests firstAcceptance tests agreed before the build starts, so done is a fact and not an opinion.Send a brief →
Delivery indexA delivery index of what was built and its evidence boundary, handed to a named owner.Send a brief →
An illustrative photograph of an office at dusk with desk lamps on
How the build runs

DESCRIBE. AGREE. BUILD.

One useful user journey with permissions, tests and handover.

01

Describe

The workflow in plain language: who uses it, what comes in, what decision follows, what must never happen.

02

Agree acceptance tests

What working means, written as tests and agreed before the build starts.

03

Build and hand over

The tool, its tests, its evidence boundary and a named owner.

Send a brief
Worked example

WHAT A DELIVERY INDEX SAYS.

DEMONSTRATION, NOT A CLIENT RESULT

Sample delivery index line, illustrative only

  • Built: the scoped user journey and its permissions.
  • Tests: the acceptance tests that ran and their results.
  • Evidence boundary: what a test run verified, and what it did not.
  • Owner: the named person who receives the handover.
Illustrative sample, not a client result.
Illustrative photograph of a desk with a laptop, a monitor and an open notebook

Illustrative sample, not a client result. Photos on this page are illustrative, not clients.

Talk to Mike →
Scope and exclusions

What is included. What is not.

Included
  • One useful user journey with permissions, tests and handover; quoted after a short brief
  • Acceptance tests agreed before the build starts; delivery index at handover
Not included
  • Not arbitrary production systems; bounded tool proof only
  • Evidence shows what a test run verified - not production readiness and not client results
Price

Scoped after a short brief

Questions

REAL QUESTIONS, PLAIN ANSWERS.

What counts as done?

The acceptance tests agreed before the build starts, plus the delivery index handed over at the end.

Do we get the tool and its tests?

Yes. The handover covers the scoped user journey with permissions, tests and handover.

Who owns it at the end?

A named owner at your firm, with the delivery index and its evidence boundary.

What must never happen?

You name it in the brief; it becomes part of the acceptance tests agreed before the build starts.

Delivery confidence

WHAT IS DELIVERED. WHO DELIVERS IT. CHECKED HOW.

Named accountability and written checks, agreed before work starts. What you can inspect is named below.

What is deliveredOne scoped internal application, client-facing app, or decision and routing tool: one useful user journey with permissions, tests and handover, plus a delivery index of what was built and its evidence boundary, handed to a named owner.
Who delivers itMike Rodgers, Rodgers Intelligence Group, Denver.
By whenTimeline agreed in the written scope before work starts.
Acceptance checksAcceptance tests agreed before the build starts: what working means, written as tests, so done is a fact and not an opinion.
If a check failsIf a written acceptance check fails, the failure is documented and reworked before handoff.
What you get to inspectThe “What a delivery index says” block is a labeled demonstration: DEMONSTRATION, NOT A CLIENT RESULT, an illustrative sample, not a client result. Evidence shows what a test run verified, not production readiness and not client results. Demonstrations on this page are illustrative, not client results. The free Client Intake Failure-Test Kit is available to run yourself.
PrerequisitesA short brief in plain language: who uses the tool, what comes in, what decision follows, and what must never happen, which becomes part of the acceptance tests.
Out of scopeNot arbitrary production systems; bounded tool proof only. Evidence shows what a test run verified, not production readiness and not client results.
Next step

SEND THE BRIEF.

Who uses it, what comes in, what decision follows, and what must never happen.

Book a free 30-minute readiness conversationSend a briefGet the free Test Kit
What to send
  • The workflow in plain language.
  • What must never happen.
  • Who should own the tool.
Photos on this page are illustrative, not clients.
What we build with

NAMED STACK. NAMED OWNER. NAMED TEST.

Each row names a layer, the technology we use in it, where the work lives in our own receipts, and the test that earned the "ran" mark on 2026-10-15. Where a layer is not used on a given project, it is left out.

Frontend
Next.js App Router + TypeScript Server components, route handlers, image optimization, and edge-ready middleware. Used on this site and a private admin surface. Evidence: rodgersintelligence.com 25 routes live plus 14 delivery-confidence pages on the same framework. Status: ran in production traffic. Test: deploy id per LIVE-PAGES.md row.
Frontend
Tailwind CSS, Geist and Inter Utility CSS for layout and density. Inter for body, Geist for code-heavy surfaces, Libre Franklin for editorial work. Evidence: rodgersintelligence.com, axe a11y check before each deploy. Status: ran. Test: zero new violations vs the wave's before-bytes.
Backend
Vercel serverless functions Edge and Node functions for the booking handoff, page-metrics ingest, and consent-recorded measurement. Idempotent handlers for every external POST. Evidence: page-metrics POST returns 204 on success. Returns 403 when consent is missing. Returns 401 when the token is missing. See the page-fix reply for the receipts. Status: ran. Test: 204 success plus the two failure paths.
Backend
Postgres for review-class data Append-only ledger for review-class evidence. Row-level roles. Used for evidence snapshots and cohort separation, not for client correspondence. Evidence: rig-evidence-snapshot-2026-10-17.json. Ingestion roundtrip ran on eleven of twelve subjects. All twelve entity pages consumed a row. Status: ran. Test: insert plus read plus role-denied path.
Program
Python (uv venv) for build-time tools uv-managed venvs house the docx, pptx, xlsx, pdf and reportlab tools. Used in the office-doc skill and the standards harness. Pinned by lockfile. Evidence: rig-office-docs skill, artifact prints in /Users/rig128gb/.rig/live/artifacts. Status: ran. Test: round-trip docx plus PDF on a sample file.
Program
Node and Bun for tooling Bun-managed scripts back the Aside browser harness and the SlopMonster checker. Node hosts the page-fixes harness. Evidence: SlopMonster tools/deslop.py returns 1 below 5/5 and 0 at 5/5. wsc2-probes.jsonl contains 31 PRIMARY Clef probes. Status: ran. Test: tested-exit script returns 5/5 on a clean draft.
No vendor is named as a partner on this page. Each row carries a receipt, scope, and a tested path. Nothing is claimed without all three. Photo on this page is illustrative.