| Best-fit project | Brand-led digital projects, websites, and marketing-adjacent apps where design and coordination matter most. | Large core systems, ERP, and integrations across many departments with long-term maintenance. | A first AI or app PoC you need working in weeks, before committing to a large build. |
|---|
| Seniority on your project | Often a senior lead plus junior staff; the people in the pitch may not be the ones coding. | Deep bench, but day-to-day work is usually staffed by mid or junior engineers and partner firms. | The senior engineer who scopes the work is the one who builds it, with no hand-off to juniors. |
|---|
| Subcontracting | Common; design, backend, or AI parts are often passed to outside vendors. Ask who writes the code. | Common on large programs, which are typically delivered across several partner firms. | None. One senior team builds it end to end. |
|---|
| Speed to first working proof | Weeks to months; timelines depend on how many outside parties are coordinated. | Months; requirements, estimation, and procurement come before code. | Weeks; a paid audit scopes it, then a fixed sprint ships a working PoC with weekly demos. |
|---|
| Code ownership and handover | Varies by contract; confirm you own the repo and not just the finished deliverable. | Often owned by the vendor or tied to a maintenance contract; full source handover is negotiated. | You own the source code. Handover includes repo, runbook, tests, and deployment notes. |
|---|