Software project feedback template
Tell us how the project went.
- Kind of form
- Feedback
- Questions
- 7
- Required
- 3
Start the 14-day trial, then choose Software project feedback under Form templates. Each field, word and colour can be changed.

Who uses it
At the end of a build the question that matters is “Did we ship what we promised?” (Yes, Mostly, No). It sits next to the required 1 to 5 rating and an optional comment about the project.
A ticked Permission box clears a comment for use on the agency’s site.
The same form, in 6 layouts
Same questions, same words. Pick the arrangement that suits the page it sits on; the layout can be changed later too.
Field guide
7 questions, each with what the business does with the answer.
| Question | Type | Required |
|---|---|---|
| Full nameNames the client contact, so the project lead can follow up on what slipped in the build. | Short text | Yes |
| EmailWhere the project lead writes back about any feature that slipped, after the automatic thank-you. | Yes | |
| Phone numberOptional, and since a low score means the owner calls, a number given here saves an email first. | Phone | No |
| Tell us about the projectOptional comment that often lists what slipped, sent with a Mostly or No to the project lead. | Long text | No |
| How would you rate us? (1 = poor, 5 = excellent)1 · 2 · 3 · 4 · 5Feedback routing logs it with every other score in its sheet, so the agency can compare builds over the years. | Multiple choice | Yes |
| Did we ship what we promised?Yes · Mostly · NoMostly and No can go to the project lead with the comment, which usually names the missing features. | Multiple choice | No |
| PermissionYou can quote my feedback on your websiteA ticked box clears the comment for the agency’s case study page or website. | Checkboxes | No |
What happens after someone sends it
Mostly is the answer to read closely, since it tends to arrive with a list of the features that slipped. A workflow can send Mostly and No answers to the project lead along with the comment. Feedback routing covers the low ratings, with a same-day alert to the owner and a note telling the client a person will call.
Made from this template, the form keeps its answers in Results: no person is added to the client’s CRM and no lead alert goes out, unless you switch “Add responses to leads” on. Any workflow you start from it still runs.
Library workflows that start from a form like this: Feedback routing and Review request.
Its answers can also go straight to another app with a starter: ActiveCampaign, Airtable, Asana, Attio, Brevo, ClickUp, Close and Discord, among others.
Trades that use it
The trade page that lists this form, with the trade’s other forms and workflows.
Workflows for software development agency
What runs when this form is sent: playbooks and packs written for the same trade.
- PackSoftware development agencyRetainer dev agency packSorts support tickets, turns requests into tasks, and recovers failed payments.
3 workflows · 12 steps · 7 apps
- PackSoftware development agencyProject-based dev agency packAnswers leads fast, briefs each call, follows up quotes and kicks off won projects.
Airtable
Calendly
4 workflows · 27 steps · 8 apps
- PlaybookSoftware development agencyAfter-hours answeringAnswer customer messages at any hour from the business’s own facts, and hand anything else to a person with a holding reply.
Telegram
5 steps · 3 apps
Related forms
See them all
Software client onboardingSoftware development agency8 fields · Registration
Marketing client feedbackMarketing agency7 fields · Feedback
SaaS customer feedback (NPS)B2B software (SaaS)6 fields · Feedback
Software project enquirySoftware development agency8 fields · Enquiry
Software project estimate requestSoftware development agency8 fields · Quote request
Developer job applicationSoftware development agency8 fields · Application
Thrum is cooking.
Get early access and you’ll be among the first in. Early members get a launch perk.




