Artist

Not signed in

Workspace

Preview mode

Saving

Saved in this browser

Muse Journey

Here's what I noticed.

This test uses 3 pricing rules, 4 boundary rules, and 4 saved reply memories before drafting.

Confidence: 80%
Missing: Confirm how the final artwork will be used.
No boundary conflict detected

Here's what I'd do: Ask the customer for missing details before quoting.

Writing style

Choose how Muse prepares replies.

Muse keeps business judgment, pricing, boundaries, missing-detail requests, and approval gates steady. Enhanced wording only changes the phrasing.

Deterministic only

Test Muse

Paste a customer message.

Generated from your training data

Using pricing rules

3 rules

Using tone

Warm, clear, and professional

Using boundaries

4 boundaries

Using saved replies

4 examples

Business read

Muse's recommendation

What Muse Understands

Scene Illustration request with 1 missing detail.

Why

Clear scope, price, deadline, usage, and references protect your time before you commit.

Business Judgment

Ask the customer for the missing details before preparing a quote.

Confidence

80% certain from the current request and your saved setup.

Next Best Action

Ask the customer for missing details before quoting.

What Muse Understands

Project

Scene Illustration

Budget

$300

Deadline

next month

Usage

TBD

What Muse still needs

Confirm how the final artwork will be used.

Pricing read

$500 – $300

Things I'd watch

No conflict detected

My suggestion

Ask the customer for the missing details before preparing a quote.

Before: rules-first draft

Hi Customer, Thanks for sharing this. It sounds like a promising fit, and I want to make sure I quote it accurately. My usual workflow is concept > sketch > color > polish, so these details will help me plan the scope clearly. Could you clarify: Confirm how the final artwork will be used? Best, Ari Vega

After: studio polish

Generate a draft to ask Muse for a more natural version.

Final safety check

Clear to approve

100% ready · 0 issues

No pricing, boundary, or policy issue found.

Draft reply