YEMPIK / STUDIOSoftware, projects and training.
All articles
Type
Guide
Topic
Method
Published
Reading time
2 min read

What should you prepare for the first meeting about a software or automation project?

Many people put off the first call because they think they need a complete document. You do not, and a document written alone often points the wrong way.

By, AI Architect & Co-Founder, Yempik
In this article
In summary
  • You do not need a specification. It is enough to know which work you want to improve, who does it today and with which systems.
  • Two or three real examples help a lot, even anonymised: a customer request, a quote, the spreadsheet that travels between departments.
  • One number changes the conversation: how many requests a month, how many hours they take, what an error costs.
  • Bring the constraints too, such as a deadline, an indicative budget or data that cannot leave the company.

All frequently asked questions →

Five things to bring

Half a page is enough. The order matters little, but if one is missing the first call goes into reconstructing it.

  • The work to improve, told the way you would explain it to a new colleague.
  • Who does it today, and who decides whether the project goes ahead.
  • The systems involved: CRM, ERP, email, shared folders.
  • Two or three real examples, with personal data removed.
  • Volumes and constraints: how often a month, by when, with what indicative budget.

If the project is about automation

Describe the exceptions: what happens when data is missing, when a customer writes in an odd format, when someone has to approve. Automation stands or falls on exceptions, and those are exactly what nobody writes down.

Say which steps you want a person to keep. Deciding up front where human review is needed costs less than finding out after launch.

What comes out of the first meeting

A shared understanding of the problem and a first idea of the work, not a finished solution. With Yempik the first call is free; if it makes sense to proceed, a proposal follows with scope, price and timeline, and if it does not, we tell you.

More questions

Do I need to bring someone technical?

No, you need someone who knows the work. If you have an IT contact, invite them, especially when access and connections to other systems come up.

Can I show confidential documents?

They are not needed for the first call. If real examples are needed later, remove names and personal data, or sign a confidentiality agreement first.

Transparency note

Answer edited by Raffaele Zarrelli, co-founder of Yempik, written with Claude. Prices, timelines and cases are the ones Yempik publishes; this page was last updated on 8 November 2026.

Shall we look at your case?

Tell us about the work you want to start from. The first call is free, and if the project does not make sense we will say so.

Book a call
What to prepare for a first software project meeting | Yempik