You do not need a technical brief to talk with MCBMichigan. A few notes about your business and an example of something you want to improve are enough to begin. You can come to the conversation before you know whether the answer is a website, an app or a change to the way you work.

Start with the part that gets in your way

Pick one problem you would most like to solve. Describe when it happens, who deals with it and what they have to do next.

For example, a repair shop might receive booking requests through phone calls, email and social messages. The difficulty could be remembering which customers have received a reply. That description gives us more to work with than a request for a new app on its own.

It also helps to describe what a better day would look like. Perhaps the owner needs to see unanswered inquiries in one place, or a member of staff needs to check tomorrow's appointments without calling someone. Keep the goal close to the work.

Bring something that shows the current process

A blank form or a screenshot can make a long explanation much easier to follow. Choose an example that shows where information arrives and what happens to it.

Useful things to have nearby include:

  • Your current website address, if you have one.
  • A blank version of a form, spreadsheet or checklist you use.
  • A sample inquiry or order, with names and private details removed.
  • A brief account of the steps someone follows to finish the task.

Use made-up details if that is easier. We need to understand the process; there is no need to bring customer records or share account passwords. If you have nothing to show, talking through a recent situation is fine.

Tell us what already works

Make a short note of the tools you rely on. Include the calendar, booking service or other software that would need to work alongside anything new. Mention who keeps those tools up to date and whether you can change their settings yourself. You do not need to research how the systems connect before the call.

Think about the people using the finished tool, too. Will someone use it on a phone between jobs? Does a member of staff need larger text or fewer steps to complete a task? Those details belong in the first conversation.

Explain the limits we need to plan around

Mention any date that matters, such as an event or the start of a busy season. Say whether it is a firm deadline or a preference. If you only have a little time to review designs or learn a new system, tell us that as well.

Bring questions about what happens after launch. Who will update the content? What ongoing services would the project need? What might those services cost? A useful plan should account for the work of keeping the result running.

We can discuss the project scope, funding options and responsibilities after understanding the need. Any available development credit and the costs you would be taking on should be confirmed before work begins.

When you are ready, request a consultation and describe the problem in your own words. Keep these notes for the conversation. A rough explanation is a perfectly good starting point.