You do not need a spec to start a useful conversation

The spec is usually the thing you do not have

People delay a conversation with an engineering partner because they believe they must arrive with a finished brief: screens, ticket lists, chosen tools, a timeline, and a budget already blessed. That is a reasonable instinct. It is also how important work waits six months while the live system keeps leaking time.

The work we take rarely starts as a specification. It starts as a product that must launch with real users, a workflow that still depends on a spreadsheet, a release that has become unsafe, or a data change nobody wants to be the last person to touch. Those are enough to begin.

If you already had a complete specification, you would not need help finding the work. You would need help executing it.

What we actually need in the first hour

We need four things. They can be spoken, sketched, or written in a short note. They do not need to be polished.

• The business outcome that would make the work worth doing — not the feature list that might produce it.
• The systems, data, and people already in the path. What exists, who uses it, and what must keep running.
• Constraints you already know: time, access, regulation, budget band, and political reality inside the company.
• The decision you need to make. Hire someone. Repair this. Rebuild that. Wait. Those are different conversations.

If you can talk about those four, we can tell you whether we are the right team, what we would need to learn next, and whether the next step is a short assessment or a scoped engagement. That is more useful than a confident guess built from a backlog.

A feature list describes intent, not effort

A backlog of screens is useful. It is rarely sufficient to price or sequence work that touches live systems. The cost usually sits in how data is shaped today, who is allowed to change it, which systems must stay in sync, and what happens when a dependency fails.

Two products can share a feature name and have nothing in common underneath. “Add invoicing” is a weekend if the ledger already exists and the tax rules are simple. It is a quarter if invoices must reconcile with a payment provider, a warehouse, and a finance team that will not accept a near-match.

How to prepare without writing a specification

You do not need a forty-page document. You need a way to walk someone through the work as it exists. The following is usually enough for a first conversation.

• A sentence for the outcome. “Customers can complete checkout without a salesperson in the loop.” “The nightly sync stops creating duplicate orders.”
• A tour of the current path. Screens, spreadsheets, inboxes, the one person who “just knows.” Record it if you cannot share access yet.
• A list of systems that touch the work, even if you only know their names.
• Incidents or near-misses from the last few months. These are better than architecture diagrams.
• What must not change. Payroll dates, a customer contract, a reporting deadline, a founder who will not migrate email.

If some of that is missing, say so. Unknowns are not a failure of briefing. They are part of the work. The failure is pretending they are not there so a quote can look tidy.

What we will not do with a thin brief

We will not invent a six-month plan from a slogan. We will not commit to a fixed price for work whose boundaries we have not seen. We will not treat a list of tools as a strategy.

We will spend one or two complimentary conversations mapping the outcome, the systems, and the risks. Then we will give you a candid fit assessment. If the work is a match, you get a written scope, a timeline, and a quote. If it is not, we will say so before either side spends more time.

A serious partner reduces uncertainty before they sell you certainty.

Bring the problem. We will help find the work.

If you have been waiting to “get the brief together,” you can stop waiting. Bring the outcome, the system as it actually is, and the thing that is getting in the way. That is enough to start a conversation that is useful to you even if we never work together.