Skip to content

Software development agency forms and automations

5 kinds of form for software development agency, each written once in the trade’s words and set in six layouts, with the packs and playbooks the library writes for the trade.

All the questions of each are below; pick a layout to see it as a customer does.

What software development agency forms collect

A software development agency builds products for clients, and its forms gather what an estimate and a first sprint need. The project enquiry asks what the person wants to build, the company, the stage (an idea, designs ready, an existing product, or the rescue of a stalled build), a budget band and a target launch date. Its description says a developer reads every enquiry and asks anyone whose production system is down to say so.

The estimate request takes the scope, the platforms (web, iOS, Android, an API or backend), specs or designs and a link to documents, which is what the agency needs to reply with a statement of work and a range. Client onboarding asks what the first release must do, the product owner, which tools the client’s team uses and where the product will be hosted.

Project feedback asks whether the agency shipped what it promised. The developer job application asks for the role, years of experience, a required portfolio link and an optional CV.

Where to start

Two packs split the agency by how it sells. The Retainer dev agency pack, for monthly support with response times per severity, has Ticket triage, Request to task and Failed payment recovery. The Project-based dev agency pack, for fixed or capped builds, has Lead rescue, Booking brief, Quote follow-up and Won-deal kickoff.

The project enquiry is the form to connect first. Lead rescue starts from it and texts the owner for “production down”, “site down”, “checkout broken” or “login broken”, and Enquiry triage can split new builds from support requests by the kinds the agency names.

The developer application pairs with Applicant intake, which can check for the portfolio link when it is listed as a must-have, and the feedback form pairs with Feedback routing. Meeting follow-up, also started by a form, turns call notes into a recap and ClickUp actions.

More forms that suit software development agency

Packs and playbooks for software development agency

Software project enquiry

Enquiry

Tell us what you want to build. A developer reads every enquiry. Production down? Say so and we call back now.

The 8 questions

  1. Full name (required)
  2. Email (required)
  3. Phone number (required)
  4. What do you want to build? (required)
  5. Company (required)
  6. Stage: Idea, Designs ready, Existing product, Rescue of a stalled build
  7. Budget: Under $25k, $25k to $100k, Over $100k, Not sure
  8. Target launch

Layouts

Software project estimate request

Quote request

Get an estimate. Send what you have. We reply with a statement of work and a range.

The 8 questions

  1. Full name (required)
  2. Email (required)
  3. Phone number (required)
  4. Describe the scope (required)
  5. Company (required)
  6. Platforms: Web, iOS, Android, API or backend
  7. Specs or designs (optional)
  8. Link to designs or docs

Layouts

Software client onboarding

Registration

Kickoff details. What we need before the first sprint. Credentials come later, through a secure link.

The 8 questions

  1. Full name (required)
  2. Email (required)
  3. Phone number
  4. What must the first release do? (required)
  5. Company (required)
  6. Product owner
  7. Tools you use: GitHub, Jira, Linear, Slack, Figma
  8. Hosting: AWS, Google Cloud, Azure, Vercel, Not decided

Layouts

Software project feedback

Feedback

How was the build? Tell us how the project went.

The 7 questions

  1. Full name (required)
  2. Email (required)
  3. Phone number
  4. Tell us about the project
  5. How would you rate us? (1 = poor, 5 = excellent): 1, 2, 3, 4, 5 (required)
  6. Did we ship what we promised? Yes, Mostly, No
  7. Permission: You can quote my feedback on your website

Layouts

Developer job application

Application

Join the team. Remote-friendly, small teams, real products.

The 8 questions

  1. Full name (required)
  2. Email (required)
  3. Phone number
  4. Tell us about something you built (required)
  5. Role: Frontend, Backend, Full stack, Mobile, Design (required)
  6. Years of experience
  7. GitHub or portfolio (required)
  8. Your CV (optional)

Layouts

Thrum is cooking.

Get early access and you’ll be among the first in. Early members get a launch perk.