Skip to main content

Questions before the bench ticket or the proof?

Here’s how uploads, routing, proofing, turnaround, and custom finish choices work before production starts.

Proof-first answers

The fastest way to calm the “what if I pick the wrong lane?” questions.

  • Products helps with family choice, the configurator handles the bench ticket, and this page answers the handoff questions in between.
  • Most anxiety lives in the handoff between intake, proof, and print, so that is where we answer clearly.
  • If the build feels too personal or too unusual for a quick answer, use contact instead of guessing.
Not sure which lane the question belongs to? Start with the first checkpoint below. All three routes still land at the same proof desk; the route only changes how much context gets attached before pricing.

Still choosing the family?

Start on Products.

Use the shelf-story board when the question is porch joke vs. pet likeness vs. premium keepsake before the option stack even matters.

Checkpoint: family fit before menu math

Already menu-ready?

Use the configurator.

If the family and finish stack are clear, send the photos, notes, props, and plaque wording through the bench ticket.

Checkpoint: the one-off is already bench-ready

Question feels heavier than a menu?

Ask for a routing read.

Deadlines, reviewers, memorial context, and launch plans should go to contact before the quote starts bluffing.

Checkpoint: the question changes the route itself

Where Questions Show Up

Most bench-ticket anxiety lives in three checkpoints.

Before upload, during proof, and before print are where the real handoff questions usually show up.

If the question is really “what should my photo pack show,” “what if the proof misses the one important detail,” or “can I still change this after approval,” this is the part of the workflow you are feeling.

Workshop note

If your question still feels more personal than procedural, route it through contact and we will treat it like a real studio request.

Build request

Reference pack and notes land in one clean build request.

Photos, notes, props, and deadlines stay together so the personal details do not disappear between inboxes, comments, or revisions.

What comes out of this stage

A quote-ready intake that makes the important details obvious.

Studio review

The studio checks fit, finish, and any missing clues.

Before the quote goes out, the team spots missing angles, memorial notes, review loops, or packaging needs that would otherwise create surprises later.

What comes out of this stage

A quote with the right questions attached instead of a vague maybe.

First proof

The first proof protects likeness before production starts.

Expression, plaque wording, props, finish choices, and character cues get one calm review while edits are still easy and affordable.

What comes out of this stage

Approval confidence before print, finishing, and packing begin.

Route the question cleanly

These are the questions that separate a calm proof stage from an email thread.

If you can answer these, the workshop usually knows whether you need Products, the configurator, or a human routing read.

  • What detail would disappoint you if the first proof missed it? That becomes the proof desk's first non-negotiable, not an afterthought.
  • Does plaque copy, a memorial date, or family wording need extra care before approval? Because wording changes can reshape the handoff just as much as color or pose.
  • Are props, florals, merch cues, or favorite toys part of the story, not just optional garnish? That tells the workshop whether the scene is decorative or emotionally load-bearing.
  • Is there a gift, memorial, or launch deadline that changes how the workshop should route the build? Routing changes early when timing pressure is real, and the FAQ should say that out loud.
If the answer points to family choice, use Products. If it points to a menu-ready one-off, use the configurator. If it points to grief, reviewers, deadlines, or “I do not know which route fits,” send the workshop a human note instead.

Easy note to copy into email

  • Subject: [project type] routing read
  • Need: [how many pieces] + [key deadline or sensitivity]
  • References: [photo count]. Key detail: [one thing the proof cannot miss]

Need a fuller example? The contact page has a workshop-ready template.

What the right route gives back

The reward is a calmer first proof, not just fewer questions.

Products gives back

A clearer family choice and the one detail the proof should not miss when the bench ticket starts.

Family board first

Configurator gives back

A live estimate, pinned references, and one proof-ready bench ticket for a calm one-off.

Build the bench ticket

Contact gives back

A human routing read; if the build is heavier than menu work, that read can turn into consult planning before pricing.

Ask the workshop

Proof trail

“For the memorial piece, the proof step gave us room to get the paw marking and plaque wording exactly right. No pressure, no rush.”

1 intake · Everything in one place