This article provides general preparation guidance. Final service recommendations depend on the actual software, data, licensing, integrations, and operating requirements involved.
Describe the outcome before the feature list
Explain what the website, script, plugin, mod, dashboard, or integration should accomplish for the people using it. The outcome helps separate essential features from optional ideas.
Identify the current platform
Include versions, frameworks, hosting environment, databases, existing code, third-party services, and anything that the new work must remain compatible with.
Separate requirements from inspiration
Reference links and screenshots are useful, but state which behaviors are mandatory and which examples are only visual direction. This prevents assumptions during scope review.
Never send secrets through the quote form
Do not include passwords, tokens, private keys, license keys, or live credentials. Secure access can be arranged only after a project is accepted and the correct process is established.
Never place passwords, private tokens, recovery codes, API keys, database credentials, or license keys into a public form or unverified message.