Project request Fit before scope
Share enough context for a useful next step.
Describe the business goal, buyer or user, current constraint, timing, and investment context. Kiwi uses the request to decide whether a conversation, a smaller discovery step, or another route makes sense.
Submitting a request does not create an engagement. Scope, fees, responsibilities, and timing are agreed in writing before work begins.
Before you send Useful qualification
A strong request has a real decision behind it.
- Good fitA defined website, product, launch, or delivery priority with an identifiable buyer or user.
- Useful contextA current constraint, decision owner, timing consideration, and evidence or assumptions you can share.
- Not required yetA finished brief, fixed scope, or polished specification. Those decisions can follow fit review.
Project request Fit, scope, and next step
Share the signal a useful proposal needs.
- Buyer context Who needs to understand, trust, or use the work.
- Business goal The outcome, constraint, and decision the project must support.
- Commercial fit Timing, investment range, and readiness for a scoped conversation.
Your request details are handled according to our Privacy notice. Cookie settings and details.