DEV Community

ArkNet Digital
ArkNet Digital

Posted on

How to price your first AI automation project (without charging by the hour)

At some point, someone who has seen what you can build with AI asks: "Could you make something like that for my business?" Then comes the hard question: "How much would that cost?"

Most developers answer badly the first time. Either they quote an hourly rate, which punishes them for being fast with AI tools, or they name a number on the spot and regret it a week later when the scope triples.

This post is a practical way to handle that first paid project: turn a vague request into a defined offer, price it in packages, and put it in a one-page proposal. It won't promise you any income. It just helps you avoid the usual mistakes.

Why hourly pricing works against you

With AI tools, you might build in six hours what used to take thirty. Bill hourly and you're charging for the slow way of doing things. Your rate also invites comparison with every cheaper freelancer on a marketplace.

The client doesn't actually care about hours. They care about the outcome: "new leads get a reply in two minutes instead of two days", or "invoices get sorted into the right folder without anyone touching them". Price the outcome and the deliverable, not the time.

That doesn't mean ignoring time. You still estimate hours privately so you know your floor. You just don't make hours the thing the client buys.

Step 1: Turn "AI stuff" into one specific offer

"I build AI solutions" is too vague to buy. A clear offer names who, what problem, and what they get:

For [type of business] that [specific painful task], I build [specific deliverable] so that [concrete outcome].

Examples of the shape (not promises of results):

  • For property managers drowning in tenant emails, I build an assistant that drafts replies to common requests for staff to approve, so routine emails take minutes instead of hours.
  • For small clinics, I build a reminder and FAQ workflow that never handles patient records in the AI tool, so the front desk answers fewer repeat questions.
  • For online stores, I build a product-description generator wired to their catalog, so new listings go live faster.

Pick one. A narrow offer is easier to explain, easier to price and easier to deliver well a second time.

Step 2: Run a discovery call before any number

Never quote on the first message. Book a short call (20 minutes is plenty) and use it to find out whether there's a real project. Questions that do most of the work:

  1. "Walk me through how this works today." You're looking for the manual steps.
  2. "How often does it happen, and who does it?" Volume and whose time it takes.
  3. "What happens when it goes wrong or gets delayed?" This is where the value is.
  4. "What tools do you already use?" Email, CRM, spreadsheets, a website builder. Integration effort lives here.
  5. "Is there any sensitive data involved?" Health, legal, financial or personal data changes what you can build and which tools you can use.
  6. "If this worked, what would be different in three months?" Their success criteria, in their words.
  7. "Who else needs to approve this, and is there a budget range in mind?" Ask it plainly. Asking about budget is normal and saves both sides time.

Write the answers down. They become the proposal.

Step 3: Price in three packages

Three tiers give the client a choice between your options instead of a yes/no on one price. A simple structure:

Starter Standard Extended
Scope One workflow, one integration One workflow, 2-3 integrations, admin view Multiple workflows or custom UI
Includes Build, test, handover doc + staff walkthrough call + monitoring setup, priority fixes
Revisions 1 round 2 rounds 3 rounds
Support after launch 7 days 30 days 60 days
Price your floor your target your target + premium

How to fill in the price row honestly:

  1. Estimate your hours for each tier, then add a buffer. First projects always surface surprises like access delays, unclear data and edge cases.
  2. Multiply by the rate you need to make the work worth doing. That's your floor. Never go below it.
  3. Sanity-check against value. If the problem costs them a few hours of staff time a week, the project should pay for itself in a reasonable number of months. If your price can't plausibly do that, either cut the scope or it isn't the right project.
  4. Make Standard the one you expect them to pick. Starter exists for tight budgets. Extended exists for clients who want more and to make Standard look reasonable.

Two rules that save a lot of grief:

  • Running costs are separate. API usage, hosting and third-party subscriptions should be on the client's own accounts or billed at cost, with a stated estimate. Don't absorb an open-ended AI bill into a fixed price.
  • Take a deposit. A portion up front (many freelancers use 30-50%) before you start, the rest on delivery. It filters out people who weren't serious.

Step 4: Write a one-page proposal

Long proposals don't get read. One page, using the client's own words from the call:

# [Project name] — proposal for [Client]

## The problem
[2-3 sentences, in their words from the discovery call]

## What we'll build
[Plain-language description of the deliverable. No jargon.]

## What's included / not included
- Included: ...
- Not included: ... (be explicit: e.g. "ongoing content updates", "new integrations")

## Options
Starter — [scope] — [price]
Standard — [scope] — [price]  ← recommended
Extended — [scope] — [price]

## Timeline
[Start date after deposit] → [first working version] → [handover]

## What we need from you
[Access, sample data, a contact person, response time]

## Terms
Deposit [x]% to start, balance on delivery. [n] revision rounds.
Running costs (API, hosting) billed to your accounts.
Changes outside this scope are quoted separately.

## Next step
Reply "Standard" (or another option) and I'll send the deposit invoice.
Enter fullscreen mode Exit fullscreen mode

The "not included" line and the "changes outside this scope" term are your protection against scope creep. When the client asks for "one small extra thing", you can say yes and point to the line: it's a separate, small quote.

Step 5: Deliver in a way that leads to the next project

  • Show something working early. A rough version in the first week builds more trust than a polished one at the deadline.
  • Hand over properly. A short doc covering what it does, how to use it, what it costs to run, and what to do when it breaks. Record a five-minute walkthrough video.
  • Ask for feedback honestly. If the client is happy, ask whether they'd give a short testimonial in their own words, and whether you can name them. Never write it for them or invent one. Fake reviews are misleading and, in many places, illegal.
  • Ask who else has the same problem. Referrals in a narrow niche are how one project becomes three.

Common first-project mistakes

  • Quoting on the first message, before any discovery.
  • Hourly pricing that makes AI-assisted speed a pay cut.
  • No "not included" section, so scope grows without limit.
  • Paying for the client's API usage out of a fixed fee.
  • Starting work before a deposit or written agreement.
  • Promising results ("this will double your leads") you can't control.

Want the templates filled in?

We put this whole path into The AI Freelancer's Client Kit. It covers the offer, a three-tier pricing table, cold outreach scripts, a minute-by-minute discovery call, the one-page proposal and a clean handover, with something to copy at each step. The process above works fine without it.

More templates and prompt packs for AI builders: veroputech.gumroad.com.

Top comments (0)