The artefact tells you the service.
Start with the artefact, not the technology.
If the artefact is a page a buyer or a salesperson can use, start with websites. One offer is a landing page. Several real offers are a business website. Edits after that are care, and only if you want them.
If the artefact is a tool people will open, start with custom software, and start with discovery unless the boundary is already written. An internal workflow tool is a business application. A first sellable product is a SaaS MVP. They are different sizes of hour. Neither is a monthly capacity block in disguise.
If the artefact is a draft or a queue with a source, start with AI, and start with a pilot. If the artefact is a handoff you can trace, start with automation. If two systems must share a record, start with integrations and name the source of truth first. If the artefact is “the small things keep breaking”, start with support, and only if the system is already known.
Search is for missing public pages, not for a promise of traffic. Capacity is for a varied queue with no single edge. If two of these are true, name the first one in the form and mention the second. We will propose two blocks.
A first block, by the sentence you can already say
Start here
“Send them the site.”
Business website, or a landing page if there is only one offer.
Start here
“Stop retyping this.”
Single workflow, or document processing if the input is a packet.
Start here
“These two lists disagree.”
Single connection, after you know which list wins.
Start here
“Draft it, I will send it.”
AI pilot, with the source named in the note.
Start here
“We need the first release.”
Discovery, then a business application or a SaaS MVP.
Start here
“It broke again.”
Support month, if we already know the system. Otherwise describe the break.