A folded signal pattern representing a structured assessment process.
What each real engagement actually examines

Interactive Assessments

An assessment page usually hides a lead-generation quiz behind a promise of instant scoring. Project scoping and a codebase assessment are the two real engagements available now, each starting from an actual conversation rather than a form.

What exists today

Two real assessment engagements exist today.

Project scoping turns a new or unclear piece of work into a priced, sequenced plan before any code changes hands. A codebase assessment does the same for a system that already exists, starting from what is actually running.

Project Scoping

For new work or an unclear brief, this turns a rough idea into a priced, sequenced plan with every assumption stated in writing.

Codebase Assessment

For an existing system, this starts from the running code and produces a plan grounded in what is actually there, not a guess.

What actually gets inspected

What each engagement actually examines.

Project scoping examines the problem statement, the constraints and the assumptions a rough brief usually leaves unstated, then sequences the work into priced phases. A codebase assessment examines the running system directly: architecture, test coverage, deployment practice and the areas carrying the most risk. Both hand back a written plan a buyer can act on immediately.

What project scoping produces

A phased plan with pricing, sequencing and the assumptions behind each phase, ready to review with a delivery lead.

What a codebase assessment produces

A written report on architecture, risk areas and technical debt, with a recommended next phase of work attached.

A quick way to decide

Which engagement fits your situation.

A new product or an unclear scope points toward project scoping. An existing system with known problems points toward a codebase assessment. Either one starts as a conversation, not a form.

Two ways to keep going

Read more before you talk to us.

The engineering guides and the case-study record are useful background before either conversation starts, and both live inside the same resource index.

See the full resource index

Guides and decks sit alongside these two engagements in one place.

Ask a specific question first

A direct question usually gets a faster answer than reading through every guide first.