How a design and engineering studio should use AI without faking the craft

Clients can smell a generated identity. They cannot always smell a generated first wireframe that a designer rebuilt. The ethical and commercial line is the same: AI speeds the boring middle. You still sell judgment, and you still stand behind the deliverable.

Where it saves hours we actually bill less for

Research dump → outline. Transcript → decision log. First-pass alt text. Test-case lists. Competitive teardowns the designer then walks. We do not hide this. We also do not charge senior rates for raw model output.

Where it does not belong

Final logo and type system. Production code that handles money. Security review. Anything the SOW says we warrant. If a junior pastes a hallucinated API into a PR, that is our miss, not “the AI.”

If a client wants AI in their product

That is a feature with a scope: one job, evals, kill switch, processor named. It is not a slide. We will price it like software because it is software. New Mexico LLC. USD. You own the repo.

How I judge whether the idea is real

I ask three questions on the first call. What job did a person do last week that you want a machine to draft? Who checks the output before a customer sees it? What happens on Friday if we turn the feature off? If you cannot answer those, we are not ready to write a statement of work. We are ready to write the FAQ or the SOP first — and that is often the actual project.

I would rather decline a fashionable chatbot than ship something that lies about hours, stock, refunds or a diagnosis. The invoice has my company’s name on it. That is why the no’s are part of the work.

What you should have in writing before you pay anyone

The job in one sentence. The data the model may see. The human who confirms. The metric you will look at in 30 days. The kill switch. The legal name of the vendor. USD price and when the card is charged. Who owns the repo. If a vendor cannot put those on one page, you are buying a demo.

• Nothing is billed by us before you approve a written scope.
• Typical project billing is 50% to start and 50% on delivery, through Stripe.
• Code, design and prompts we write for you transfer on final payment.

The steps — do these in order

1. 01

   List the hours you currently waste on first drafts

   Research dumps, transcripts, alt text, test lists. That is the circle.

2. 02

   Use a model there, and show the client the rebuild

   They are paying for judgment. Do not hide a generated logo as craft.

3. 03

   Ban production money paths from paste-driven code

   If it charges a card, a human reviewed it.

4. 04

   Price the boring middle cheaper

   Do not charge senior rates for raw output. Charge for the pass that makes it yours.

5. 05

   When a client wants AI in their product, write a feature SOW

   One job, evals, kill switch, processor named. Not a slide.

6. 06

   Keep a kill switch on client-facing experiments

   Your brand is on the work. A hallucinated hours page is your incident.

7. 07

   Put ownership in the contract

   Repo, prompts, Figma. Same as any other deliverable.

8. 08

   Decline the content farm

   If the brief is 500 city pages, the call is already over.

Keep reading

• Think. Build. Ship.

  Think. Build. Ship. — the only order that produces a product

  Think is understand the problem. Build is engineer the solution. Ship is put it into the real world. Skip one and you have a tutorial, a file, or a pitch — not a product.

• Tutorials

  Tutorials are not a product. A link is.

  You can finish a hundred tutorials and still have nothing to send. Shipping is a link that does a job — that is what SINLE Academy is for.

• Bootcamp

  SINLE Academy is not a coding bootcamp

  No job promise. No certificate as the product. Eight people, six weeks, $400 — you leave with work someone can use, not a placement story.