# Start with the right size of commitment.

> A meaningful technology initiative does not always need a six-month contract on day one. Some are ready for implementation. Others need a key architecture, product or data question answered first.

Canonical URL: https://marmation.com/engagements/

## The decision

What can you responsibly commit to next?

Fund the decision that is still open, the assumption that needs evidence or the implementation boundary you can already define. The right starting point follows what is known.

## The situation behind the request

A company may have a funded product roadmap and only need a qualified implementation team. Another may be comparing managed and private inference, with no agreed requirements. The appropriate purchase decision differs.

## Where the obvious solution falls short

Open-ended consulting can delay delivery. Overconfident fixed-price statements can create expensive change orders after dependencies are discovered. A responsible engagement model makes uncertainty visible before it becomes a contract dispute.

## How we would approach the work

Marmation uses defined decision sprints, validation builds, implementation milestones and, where appropriate, dedicated engineering capacity. The contract states responsibilities, IP, third-party fees, acceptance and handover.

## What the engagement may include

- Decision and architecture sprint with a concrete options record.
- Product validation and technical feasibility slice.
- Scoped production build with acceptance and release plan.
- Time-bounded engineering capacity for evolving product work.

## The choices worth making explicitly

An architecture sprint is not mandatory when the client provides enough technical clarity. A production promise is not responsible when access and dependencies are unknown.

## What we would test before calling it ready

Review the estimate against discovery, UX, architecture, security, integrations, QA, deployment, data, documentation and warranty. The operating model should be transparent before work begins.

## A sensible first step

Tell us where the initiative stands and what decision is blocking it. We can determine a focused first engagement.

## Related reading

- [Resolve the question before funding the build.](https://marmation.com/engagements/decision-and-architecture-sprint/)
- [Prove the important part before scaling the investment.](https://marmation.com/engagements/product-validation-build/)
- [Ship a working system with a defined boundary.](https://marmation.com/engagements/production-implementation/)