PRODUCT
How an inquiry becomes a quote-ready job.
Markyard reads what a customer sends, works out what is missing, checks the artwork, and prepares a priced job from your own catalogue and prices. Every step below is a real stage in that path, not a marketing category.
- Quoting today
- 20 min to 3 hrs
- Markyard target
- ~5 min
THE CORE FLOW
One thread, eight checkpoints.
Every inquiry moves through the same eight checkpoints, in the order shown here. Nothing skips ahead, and nothing reaches a customer until a person has looked at it.
Inquiry arrives
- In
- An email in your Gmail, in whatever shape it arrives: a forward, a reply, a signature block, an attachment.
- Out
- The message appears in Markyard as one inquiry, linked to its full thread and never pulled in twice.
- Why
- Your inbox stays exactly where it is. Nothing gets copied out or forwarded by hand.
Markyard extracts the job details
- In
- The raw thread, forwards and quoted replies included.
- Out
- Structured fields, product, quantity, size, colour, print method, position and deadline, each with its own confidence score.
- Why
- You read five labelled fields instead of a wall of forwarded text.
Illustration of extracted job fields, each with a confidence score. Sample data, not a live account. Extracted
ProductT-ShirtsHighQuantity250HighDeadlineMay 29MediumPrint methodNot statedLowMissing information is identified
- In
- The fields extraction just produced.
- Out
- An explicit, specific list of what is missing or unclear, not a general warning.
- Why
- This is the part of Markyard built first and tested hardest: catching a gap before a price gets guessed at, not after.
Illustration of a missing-information list for one job. Sample data, not a live account. 2 fields missing
- Print method not stated
- No artwork attached
Everything else is ready.
Markyard prepares the next response
- In
- The missing-information list.
- Out
- A draft reply that asks for exactly what is needed, in the tone learned from quotes you have sent before.
- Why
- Nobody starts from a blank compose window to ask two questions.
Artwork is checked
- In
- The file attached to the inquiry.
- Out
- A verdict, print ready, needs work, or unusable, with the specific reason: file type, DPI at the actual print size, colour count, transparency, vector or raster.
- Why
- A promise of exact reproduction is only made when the source can back it up.
Illustration of the artwork honesty table: what the source of a file allows Markyard to promise. Sample data, not a live account. Source determines the promise
SourceActionPromiseVector fileConverted1:1, any sizeClean, high-res rasterBackground removed, resized1:1 in practiceSmall or blurry rasterRedrawn, flaggedMarked as redrawnA human reviews
- In
- Whatever Markyard has prepared so far: the draft reply, or the finished job.
- Out
- An approval, or an edit first. Nothing moves on without one or the other.
- Why
- This gate sits in the database, not only in the interface. There is no path around it.
The job becomes quote ready
- In
- Complete job details, a clear artwork verdict, and your own catalogue and prices.
- Out
- A priced draft, built from numbers you entered, with margin visible line by line.
- Why
- This is the step behind the 20 minutes to 3 hours dropping toward roughly 5 minutes.
Illustration of a quote-ready job with priced line items. Sample data, not a live account. Quote #1024
Quote ReadyT-Shirts (250)€1,600Screen print, 1 colour€420Setup fee€60Total€2,080Margin 24%, from prices you set.
Handoff
- In
- The approved reply or quote, exactly as reviewed.
- Out
- One message, sent from your own connected address, into the same thread the customer already has open.
- Why
- The customer notices nothing new to learn, and your production and accounting tools stay exactly where they are.
CAPABILITIES
Everything the flow is built from.
The eight checkpoints above are made of these. Four have their own page; the rest are shown here in full.
Smart Inbox
View the pageProblem
Inquiries arrive scattered across forwards, replies and signatures, and someone has to open every one just to know what is inside.
What Markyard does
Pulls every inquiry into one operational inbox, deduplicated and linked to its full thread, with a status: new, in progress, answered or closed.
What you see
A list of inquiries with status and extracted highlights, and the original thread beside the extracted data.
Result
One place to work from, instead of a mailbox where the real information is buried in reply chains.
Inquiry extraction
Problem
Reading a messy email for product, quantity, size, colour, method, position, deadline and contact takes real time, every single time.
What Markyard does
Runs extraction on the actual thread, forwards and signature included, and returns structured fields with a confidence score per field.
What you see
The extracted fields beside the original message, with the raw model output kept for anyone who wants to check the reasoning.
Result
A five-second read replaces a five-minute one.
Missing information
Problem
A quote built on a guess about print method or size is a quote that has to be redone.
What Markyard does
Compares what is extracted to what a quote needs, and flags exactly which fields are missing or ambiguous.
What you see
A short, specific list, not a vague warning: print method not stated, no size run given.
Result
The gap gets closed with one targeted question instead of a guess.
Draft replies
Problem
Composing a reply that asks for the right two things, in your own voice, is slow to get right from a blank page.
What Markyard does
Prepares a draft asking exactly what is missing, in the tone learned from quotes you have sent before.
What you see
A draft, ready to read, edit or send, not a template full of brackets.
Result
A reply goes out in the time it takes to skim it.
Human approval
Problem
An AI that emails a customer on its own is a liability, not a convenience.
What Markyard does
Locks every outbound message behind an approval step at the database level, not only in the interface, so nothing reaches a customer unclicked.
What you see
A review screen before every send, with the option to edit the text first.
Result
The judgment stays with the person who knows the customer.
Artwork check
View the pageProblem
Whether a logo is fit to print does not show up by looking at it in an email client.
What Markyard does
Reads file type, pixel dimensions, DPI at the actual print size, colour count, transparency and vector versus raster, and rates the source honestly.
What you see
A verdict, print ready, needs work, or unusable, with specific problems listed, and the original next to the redrawn version whenever something was redrawn.
Result
You never promise 1:1 reproduction a file cannot deliver, and never send an unprintable file to press.
Quote-ready jobs
View the pageProblem
Pricing a job by hand means reopening a spreadsheet and doing the same maths every time.
What Markyard does
Matches the job against your own catalogue and prices, quantity tiers and print surcharges, all entered once, and marks it quote ready the moment nothing is missing.
What you see
A priced draft with every line item visible, built from numbers you set, not numbers Markyard guessed.
Result
Quoting moves toward the five-minute target, with margin analytics you could not calculate by hand before.
Customer context
Problem
Knowing whether the last few quotes sent to a customer actually turned into jobs used to live in memory, not in a system.
What Markyard does
Keeps the inquiries and quotes of each customer together, and rolls up outcomes once you record whether a quote was won or lost.
What you see
Past requests and outcomes for the current customer, shown next to the current inquiry.
Result
Pricing and follow-up decisions use your own history, not a guess.
Automations
View the pageProblem
Following up on a quote that has gone quiet is easy to forget and repetitive to do by hand.
What Markyard does
Runs simple rules against the status of a job, for example a follow-up after a set wait with no reply, or a reminder before a deadline.
What you see
A short, readable list of the rules in plain language: when, then, wait.
Result
Fewer jobs go quiet for the wrong reason.
Handoff
Problem
A tool that hands a customer to a separate portal, or that needs new downstream software, is a second thing to learn.
What Markyard does
Sends the approved reply from your own connected Gmail address into the same thread the customer already has open.
What you see
One continuous email thread, exactly as the customer already sees it, with your own name and address on it.
Result
The customer notices nothing different, and your production and accounting tools stay exactly where they are.
FAQ
Quick answers about how it works
Ready to see it against a real inquiry, or talk through your own workflow first?