What Happens on a Discovery Call, and What You Get After

A discovery call is a 20-minute conversation about what you want built, before anyone writes a plan. We use it to map your goals, your constraints and the systems the software must connect to. Afterwards, you get a recommended team, a timeline and a delivery plan with clear milestones.

1. 01How to book one

   You can book a 20-minute call from our contact page, or send us a message. We reply within one business day.

   A few lines beforehand help: what the software should do, who will use it and any deadline. You don’t need a written specification.

   From our side, a founder and a senior engineer join the call, so business and technical questions get answered on the spot.

2. 02What helps to have ready

   1. The problem the software solves, and for whom.

   2. What you use today: spreadsheets, an old app or a tool you’ve outgrown.

   3. The systems it must connect to, such as payments, a CRM or accounting software.

   4. Who will use it, and on which devices.

   5. What a good result looks like six months after launch.

   6. Any deadline, and what is driving it.

3. 03What most people haven’t worked out yet

   Most clients don’t have every answer when they book, and that is normal. These four come up most often.

   1. Integrations: which systems the software has to connect to.

   2. First release: what to build first, and what can wait.

   3. Maintenance: who looks after the software after launch.

   4. Timeline: how long it will really take.

   Working these out is the point of the call. You don’t need the answers before you book.

4. 04Why integrations come up so often

   In our portfolio, the longest builds connected to the most outside systems. BuffyHub syncs with Amazon, eBay and Walmart. AutoBuffy connects payments, shipping carriers and vendor inventory.

   So expect questions about what the software must talk to. The answers tell us more about the timeline than the number of screens does.

5. 05What you get after the call

   Within two business days, you get three things: a recommended team, a timeline and a delivery plan with clear milestones. If you want engineers to join your own team instead, you get a shortlist within 2 days and interview them yourself.

   Most of our custom software projects take three to six months to build, and simpler ones take one to three. The plan says where yours sits, and why.

6. 06Once work starts

   Our engineers join your workflow, and you see working software in a weekly demo, checked against the milestones in the plan. You own everything they write for you, including the source code and the intellectual property in it.

7. 07If you don’t need custom software

   The call doesn’t commit you to anything, and there is no long-term contract to start. If an existing tool fits better, we will say so. For a US bookkeeping firm, we set up GoHighLevel instead of building a custom CRM.