What to Include in Your Enquiry
A useful enquiry gives enough context for a productive first conversation. You do not need a finished specification — a clear description of your product idea, who it is for and what you need is a good starting point.
01
Your Product Idea
What is the software you want to publish? Describe it in plain terms — what it does, who uses it and what problem it solves. An application, a platform, a business tool, a digital product concept or an internal system are all valid starting points.
02
Target Users
Who will use the software? How many user types are there? Are they internal staff, external customers, business clients, the general public or a combination? User groups shape scope, access, data handling and documentation requirements.
03
Key Features or Requirements
What are the core things the software must do? A rough feature list — even if not prioritised — helps scope the conversation. You do not need a detailed functional specification at this stage.
04
Publishing Goals & Expectations
What does success look like for this software? Is it an internal tool for operational use, a commercial product for public release, a concept being evaluated or a system replacing an existing process?
05
Any Known Constraints
Are there specific timelines, budget considerations, integration requirements, data handling obligations or compliance areas you are aware of? These help structure the initial discussion appropriately.
Important: Do Not Submit Sensitive Data
Please do not include passwords, API keys, private customer data, sensitive database exports, source code secrets, payment details, access credentials or security vulnerabilities in your enquiry. Enquiry forms are not appropriate channels for sensitive information of this kind.