How Biddy learns your pricing

The pricing interview captures the structural side of how you price — your day rate, multipliers, overhead, profit. But every contractor has rules that don't fit into a table. "Never quote less than $1,200 for a small bath demo." "Always add a 20% bump on natural stone." "Charge a $250 dump fee on any job that produces a full container." When you tell Biddy a rule like this in conversation, it offers to save it — and from then on, that rule applies to every future proposal automatically.

How rule capture works

When you tell Biddy a generalization in plain English, it recognizes the shape of a rule and proposes saving it. The trigger phrases are the ones you'd naturally use:

• "always"
• "never"
• "every time"
• "whenever"
• "for any X"
• "I usually"
• "I never"

If Biddy spots one of these in your message, it'll come back with a confirmation card: "Save this as a pricing rule for every future proposal? <rule text>" with Confirm and Reject buttons.

[!tip] Tap Confirm and the rule lands in your pricing settings. Tap Reject and Biddy treats it as a one-time edit to the current proposal only.

Two kinds of rules

Biddy distinguishes between two scopes:

• Org-level rules — apply to every proposal across every service. "Never quote glass tile patterns under 1.6 difficulty." "Always add 10% rush charge for jobs starting within 2 weeks."
• Per-service guidance — applies only to one specific service in your catalog. "For shower waterproofing, always include a 12-month leak warranty in the scope." "Demo lines should never go below $1,200."

Biddy figures out the right scope based on what you said. If your message names a specific service, it goes per-service. If it's a cross-cutting rule, it goes org-level.

Where saved rules live

To see what Biddy has captured for you, go to Settings → Pricing templates and tap the Pricing rules tile. Biddy's rules sit in the same list as the rules you wrote yourself, each with a From Biddy stamp. A per-service rule also says which service it's for.

[!steps]

1. Open Settings → Pricing templates and tap the Pricing rules tile
2. For a Biddy rule you no longer want, tap Hide. It stops applying to proposals right away
3. Hidden rules wait under Hidden at the bottom of the panel. Tap Restore to put one back into service
4. To clear a hidden rule out for good, tap Delete

Hide, Restore and Delete on Biddy's rules save right away. Your own rules are edited in the same list and saved with the panel's Save button.

Next to it, the Biddy's alerts tile is where you tune how eager Biddy is about flagging pricing patterns: how far your real prices have to drift before it speaks up, how many similar lines it wants to see first, and how many days a dismissed alert stays quiet.

Per-service guidance lives on the service detail page itself — go to Services, click into the service, and you'll find a Pricing Guidance card with everything Biddy has captured for that service. (On a service priced as a range, the same card is titled Pricing Map.)

How rules show up in proposals

When you generate or regenerate a proposal, Biddy injects your active rules into the AI's instructions before it writes a single line. The AI sees them as binding constraints. So a rule like "never quote small bath demo under $1,200" literally prevents the AI from emitting a demo line under that floor — even if its raw math would suggest less.

[!note] Rules don't fight your data. If a rule says "minimum $1,200" but the AI's calculation lands at $1,800, the AI still uses $1,800 — the rule is a floor, not an override. Rules only kick in when the AI's first pass would otherwise violate them.

Drift detection

If you build a service one way in the catalog but then consistently edit proposals away from that base price, Biddy notices. Every proposal you send counts once for each catalog service on it, at the price you actually sent. After 5+ jobs where your real proposals diverge from your catalog price by more than 15%, Biddy will surface a suggestion on your dashboard — "your shower waterproofing service is averaging $X but you're quoting $Y in practice. Update the base price?" The price you saved on the service doesn't count as one of those jobs.

This is opt-in. Biddy never silently changes your catalog. It just flags the drift so you can decide.

[!warning] Drift suggestions don't fire on individual edits — only on patterns. One weird high-priced proposal won't trigger anything. Five proposals consistently 20% higher than the base will.

Why this matters

The whole point of BidCraft's pricing system is that you only have to teach it once. The pricing interview captures the structural rules; conversational rule capture catches everything else. Over time, your AI starts to feel less like a generic tool and more like a foreman who knows how you run jobs.

Next steps

Once your pricing is teaching itself, the next move is mastering the proposal editing workflow — see Asking Biddy to make changes. If your pricing interview still has gaps, The AI pricing interview — Advanced is where the remaining 40% lives.