Start a scoping conversation
Tell us about the system or the problem. We will tell you honestly whether we are the right people to build it.
What happens after you write
No funnel, no sales development rep, no sequence of nurture emails. Here is the actual process:
- You get a reply from Dan. The founder reads every inquiry personally, because the person who answers you is the person who would build your system.
- A short call. Usually 20 to 30 minutes: your problem, your systems, your data as it actually is. If we are not the right fit, we say so on this call and, where we can, point you somewhere better.
- A characterization proposal. If it makes sense to continue, you receive a written proposal for a characterization stage: what we will map, what it produces, and the success metrics (KPIs) that will judge the work. Characterization can end with “AI is not the right tool here” or “your data is not ready yet”, in writing. That answer comes at the characterization stage, not after a failed project.
What to include for a fast, useful reply
You do not need a specification document. Two or three sentences covering:
- The problem in business terms. “We over-purchase and sit on dead stock”, “sales planning runs on gut feel”, “our operation lives in WhatsApp groups”. Plain language beats AI vocabulary.
- The systems you run. ERP (Priority, SAP), CRM, monday.com, spreadsheets, a closed network. Integration is usually the real question, so this saves a round trip.
- What data exists, roughly. Years of order history? Images? Nothing structured yet? “We are not sure” is a perfectly good answer.
A note on confidentiality
Most of our work is under NDA, and several engagements run inside closed networks. Whatever you write here is treated accordingly: no mailing lists, no sharing, no naming you anywhere without written permission.