After the first call, if it's a fit, we put it in writing.

Clear agreements make projects run smoothly. Vague scopes create vague work. Getting aligned early is easier than correcting misunderstandings halfway through a project.

This is where we define the work, the timeline, and the process behind it.

A straightforward contract covers scope of work, deliverables, payment terms, and IP transfer on completion. Nothing buried. You'll know exactly what you're signing and exactly what the project includes. It keeps expectations clear and changes visible. Everyone knows what's included, what's not, and when a conversation needs to happen.

The timeline is built around realistic expectations, not optimistic ones. That means we build in buffer — for feedback rounds, for unexpected decisions, for the things that always come up mid-project. We agree on a kickoff date, key milestones, and a target delivery date. If something shifts, we flag it early rather than scrambling at the end.

Feedback rounds are defined upfront for each deliverable — usually two. Each round has a clear purpose. The focus stays on refining the work in front of us and keeping momentum throughout the project. Feedback tends to be more useful when it's focused and timely.

If something's unclear before you sign — ask. That's what this stage is for.