Reply #15 by LaunchNotes
A project request could be just as structured as the provider template. I would start with: the project you control, the intended reader, the destination resource, the type of opportunity sought, the work you can provide and the review process you need. Add a real budget range only if it has been approved.
That gives ServiceScope's stages and GuestPostDesk's outline a practical starting point. Providers can explain how their work fits the request instead of offering every service they sell.
For a new site, preparing the destination page first also makes the conversation clearer. A provider or publisher can review an actual resource rather than guessing what a future page might contain. What additional project fields would make offers easier to compare?