You do not need a finished specification before contacting a development company. The first message should explain the business situation well enough for the recipient to ask useful questions and suggest an appropriate next step.

Do you keep postponing the first message?

Many teams know the operation they want to improve but do not know the correct technical terms. They may receive requests through phone, chat, email, and paper, copy them into a spreadsheet, and worry about missed replies. That is already valuable context.

The short answer

Include seven items:

  1. The current problem.
  2. The current workflow.
  3. The people who use or manage it.
  4. The first flow you want to improve.
  5. Examples or documents you can share.
  6. What has not been decided.
  7. What you want to decide in the consultation.

Write “to be decided together” where necessary. Hiding uncertainty makes the estimate less reliable.

A request message is not a specification

The first contact does not need database fields, screen diagrams, or a complete list of exceptions. It needs a clear purpose and enough operational detail to decide whether the next step is a SaaS configuration, a prototype, discovery work, or a production estimate.

Avoid presenting guesses as fixed requirements. “We think a mobile app may be needed because field staff use phones” invites a useful discussion. “A native app is mandatory” may close off a simpler web solution before the problem is examined.

Four practical ways to start the conversation

Short inquiry: best when you only need to confirm fit. Include the problem, target users, and preferred next conversation.

One-page workflow note: useful for comparing partners. Add current steps, handoffs, pain points, and the first desired result.

Annotated samples: attach a redacted paper form, spreadsheet, or email template. Real examples reveal rules quickly.

Prototype brief: use when the main goal is to test screens or a workflow before requesting a production estimate. State the decision the prototype must support.

Seven items for the first request

1. Describe the problem

Write what is being lost: time, accuracy, visibility, response speed, or customer experience.

2. Describe the current flow

Use arrows or numbered actions. Include copying between tools and manual confirmation.

3. Name the users

Distinguish customer, operator, manager, and external partner when their access differs.

4. Choose the first improved flow

Do not ask to digitize the whole business at once. Select one complete flow that can show value.

5. List existing materials

Mention current forms, tables, message templates, reports, and service accounts. Redact personal information before sharing.

6. State what is undecided

Budget, detailed design, integration method, and release date can remain open. Explain any hard deadline or spending limit you already know.

7. State the decision you need

Ask whether an existing service is sufficient, whether a prototype is sensible, and what information is needed for a reliable estimate.

A request that is difficult to answer

We need a reservation system with login, payments, notifications, reporting, and an admin panel. Please tell us the price and delivery date.

This does not show users, booking rules, current tools, transaction volume, or which feature creates value. A better message connects features to the operation and identifies what can wait.

Checklist before sending

  • [ ] The business problem is one or two sentences.
  • [ ] The current workflow is understandable without technical terms.
  • [ ] First users and one target flow are named.
  • [ ] Required data and sensitive information are mentioned.
  • [ ] Existing tools and sample documents are listed.
  • [ ] Known constraints and undecided items are separated.
  • [ ] The question for the first consultation is explicit.

Copyable request template

Subject: Consultation about improving [workflow]

We currently handle [work] using [paper/email/chat/spreadsheet]. The main problem is [missed response/re-entry/time/visibility]. The current flow is: [step 1] → [step 2] → [step 3]. The first users would be [roles and approximate number]. We first want to improve [one complete flow]. We can share [redacted forms, tables, message samples]. [Budget/design/integration/timing] is not decided yet. In the first consultation, we would like to decide whether [SaaS/prototype/custom development] is the appropriate next step and what information is needed for an estimate.

Your next step

Spend fifteen minutes writing the current flow and attach one redacted example. Send the message before trying to complete every specification. The quality of the partner's follow-up questions is itself useful selection evidence.

Further reading

Before sharing materials, follow your organization's privacy and security rules. For later requirements, use authoritative accessibility, security, and platform documentation that matches the actual product rather than copying a generic specification.