Rough notes are fine

Tell us where the work gets stuck

Describe the workflow that takes too much chasing, checking, or re-typing. Rough notes are fine: we will ask the right questions on the call.

What happens next

1
We read it and reply
A person on the team reads your message and replies with a few questions and times for a call.
2
Discovery call
We walk through the workflow, the people involved, and the tools it runs through today. No preparation needed.
3
A clear first step
You get a short written summary: what we would build first, and what it would change for the team.

Questions

Anything else, put it in your message and we will answer on the call.

What should I put in the message?

The workflow that frustrates you most, who is involved, and the tools it runs through today. A few sentences are enough to start.

Do we need to know what we want to build?

No. Most people describe a problem, not a solution. Mapping the workflow is how we find the first thing worth building.

Can you work with the tools we already use?

Usually, yes. We connect the systems you have where we can, and only suggest replacing a tool when it is the bottleneck.

How big does a first project have to be?

Small is better. Every engagement starts with one workflow and a focused first release, then grows from what it changes.

Is the discovery call a sales pitch?

It is a working conversation about your workflow. If we are not the right fit for it, we will say so.