A feature request form covers contact details, what needs building, what systems it touches, and any target release date for estimating effort and risk.
A small feature sounds straightforward until someone opens the codebase and finds edge cases, brittle integrations, and missing context, which is how “quick” turns into rewrite. The Feature Request Form gives a client one place to describe what they want in enough detail to talk about effort and risk before anybody commits, and the headings sit in Zilla Slab with olive accents and a blue call to action so the questions read like instructions, not a chat.
The form opens with a short note about estimating effort and risk for mobile app development, then moves into contact details and the request itself. The About this request section asks for what must not change and any deadlines, and the rest of the questions pin down whether an existing app needs review, what feature needs pricing, and which systems the change will touch, so the estimate doesn’t ignore login, payments, or backend dependencies.
- Feature Request Form A short intro tells the client what the questions are for and sets expectations around effort and risk.
- About this request A written prompt asks for what the feature needs to do, what can’t change, and any deadlines.
- App review choice A required question confirms whether pricing is based on reviewing an existing app, a spec only, or an unsure starting point.
- Feature and systems Two required long-answer questions collect the feature details and which systems the change will touch.
- Target release date An optional date field captures a target release date when the client has one.
Once the form is in your workspace, you share it like other forms that collect answers and files, and each submission lands as a response you can review and reply to with next steps. The only edits are your own wording in the intro blocks and the questions you want to make required or optional for your intake.
We went from spending hours on every proposal to creating fully customized ones in under 5 minutes. That's not an exaggeration - we timed it.
What to include in a feature request form
| Part | What it covers |
|---|
Feature Request Form | An opening note frames the form around estimating effort and risk for mobile app development, and you adjust the wording to match how you run intake. |
Your name | A required name field identifies who to follow up with. |
Email address | A required email field gives you a reliable reply address for next steps. |
Phone number | An optional phone field collects a number when a call is the fastest way to unblock details. |
About this request | A written prompt asks for what the request needs to achieve, what must not change, and any deadlines. |
Do you want us to review your existing app? | A required choice records whether you’re reviewing an existing app, pricing from a spec only, or advising on the best approach. |
Describe the feature you want priced | A required long-answer field collects the feature description in the client’s own words. |
Which systems will this touch? | A required long-answer field calls out dependencies, including backend services and other connected systems. |
Target release date, if any | An optional date field captures timing when a release window matters, including App Store submission targets. |
Who it is for
Mobile app agencies, product studios, and freelance developers who need a consistent intake before quoting iOS development, android development, or cross-platform apps work.
The form in full
Feature Request Form
Use this form to describe the feature you want so we can estimate effort and risk for mobile app development. We’ll review your answers and reply with next steps.
- Your name (required)
- Email address (required)
- Phone number
About this request
Tell us what you want, what must not change, and any deadlines.
- Do you want us to review your existing app? (required)
- Yes, review the existing app
- No, price from a spec only
- Unsure, please advise
- Describe the feature you want priced (required)
- Which systems will this touch? (required)
- Target release date, if any
