AI woven through the workflow
Not a chat window bolted onto the side. AI is a design principle intended to show up inside communications, quoting, artwork and production.
Built for the printing industry · Preparing for beta
The operating system we’re building for print businesses.
From the first customer conversation to fulfillment, CMYK Pro is being developed to bring print workflows together—with AI and tailored setup at its core.
CMYK Pro is in active development. A working platform exists; individual capabilities are still being verified ahead of beta.
Job 2417 · Harbor Street Run Club
Beta in preparationIllustrative concept
Stage 01 / 05 · Information received
An email becomes a job, not a to-do.
Request from Dana OkaforDetails structured
“Hi! We need 144 heather navy tees for the spring 10K — our 3-color logo on the front, the small mark on the left sleeve. Could we pick up Friday?”
144 pcsHeather navyFront · 3 colorsL. sleeve · 1 colorDue Friday
Intended: Your team confirms anything the request left unclear.
Illustrative concept with fictional data. Not a product screenshot; capabilities shown are intended, not verified.
Designed for shops in
- Screen printing
- Embroidery & apparel decoration
- Signs & wide-format
- Commercial & digital print
- Related print production
01The vision
One shop. One connected workflow.
Job 2417 is ordinary: 144 heather navy tees, front 3-color + left sleeve 1-color, friday pickup. That’s the point. Ordinary jobs are where the handoffs pile up.
- 01
The job lives in six places.
A quote in a spreadsheet, artwork in an inbox, the order on a whiteboard, the PO in someone's head. Every handoff is a chance to re-key something wrong.
- 02
The front office and the floor see different jobs.
Sales promises a ship date. Production finds out at the press. Nobody is wrong, but nobody is looking at the same thing.
- 03
Admin quietly eats the margin.
Chasing approvals, answering “where's my order,” re-checking garment counts. Necessary work that rarely gets anyone closer to printing.
02Follow one job
Job 2417, from inbox to pickup.
The same illustrative job from above, slowed down. Each stage shows what tends to happen today, what CMYK Pro is intended to do, and what it hands to the next person. A concept of the vision — not a list of live features.
Stage 01 · Information received
An email becomes a job, not a to-do.
Dana’s request lands at 7:40am, between a reorder and a supplier invoice.
- Today
- Someone reads it, copies quantities into a spreadsheet and hopes the sleeve note survives.
- Intended
- The request is intended to be read into structured details — garment, count, locations, date — attached to one job record.
Your team confirms anything the request left unclear.
Request from Dana OkaforDetails structured“Hi! We need 144 heather navy tees for the spring 10K — our 3-color logo on the front, the small mark on the left sleeve. Could we pick up Friday?”
144 pcsHeather navyFront · 3 colorsL. sleeve · 1 colorDue FridayIllustrative · hands forward: Customer, garment, quantity, locations and due date
Stage 02 · Draft prepared
The estimator reviews instead of rebuilding.
Your estimator knows the pricing rules. They shouldn’t have to retype the order to apply them.
- Today
- The quote is assembled from scratch in another tool, and the details are keyed in a second time.
- Intended
- A quote draft is intended to be assembled from the job details using the pricing logic configured with your shop.
Nothing is sent until the estimator approves it.
Arrives with: Customer, garment, quantity, locations and due date
Quote draft · Job 2417Awaiting estimatorIllustrative quote draft lines, quantities only Line Qty Heather navy tee, S–XL 144 Front print, 3 colors 144 Left sleeve, 1 color 144 Screen setups 4 Pricing rules configured with your shop. Values omitted in this concept.
Illustrative · hands forward: Line items, setups and the draft customer reply
Stage 03 · Review requested
The proof and the conversation stay on the job.
Proof v2 moves the sleeve hit. Friday only holds if Dana approves today.
- Today
- Proof versions live in an inbox thread. The floor finds out about the change at the press.
- Intended
- Proof versions, comments and the approval request are intended to sit on the same record the floor will read.
The customer approves. Your team decides when it moves.
Arrives with: Line items, setups and the draft customer reply
Proof v2 · front + sleeveWaiting on customer- v1 · sleeve at 4.0″
- v2 · sleeve raised 0.5″
- Front: navy, white, gold
Suggested reply · for review
Hi Dana, proof v2 raises the sleeve mark half an inch. Approve today and Friday pickup holds.
Illustrative · hands forward: Approved artwork version and the change note
Stage 04 · Production handoff
The floor sees the job the front office sold.
Your press operator needs screens, ink colors, blanks and placement — not a forwarded email.
- Today
- A printed ticket gets rewritten by hand, and the sleeve change is a sticky note.
- Intended
- On approval, the job is intended to hand off with specs, art and blank status already attached.
Production leads set the schedule.
Arrives with: Approved artwork version and the change note
Floor ticket · Job 2417Handed to production- Proof v2 approved
- Blanks received · 144 / 144
- Screens: 3 front, 1 sleeve
- Sleeve change noted on ticket
Illustrative · hands forward: Specs, art, blanks received and the run sequence
Stage 05 · Fulfillment
The loop closes where it started.
Dana shouldn’t have to call to ask if Friday is still on.
- Today
- Pickup is confirmed by phone, and the job details disappear into a closed folder.
- Intended
- A pickup update is intended to be drafted from the job’s real status, and the record kept for the reorder.
Your team reviews the update before it goes out.
Arrives with: Specs, art, blanks received and the run sequence
Pickup · FridayVisionPrintedPackedPickupSuggested update · for review
Hi Dana, your 144 tees are packed. Pickup is ready Friday after 10am.
Job history kept for the next reorder.
Illustrative · hands forward: A job history ready for next season’s reorder
03One record, every department
Built around your print business, not the other way around.
Job 2417 touched three parts of the shop. The vision is that all three read the same record.
Front office
- Customer conversations
- Quoting & pricing
- Proofs & approvals
Operations
- Orders & job tracking
- Purchasing & receiving
Shop floor
- Production planning
- Shipping & pickup
AI assistance intended across all three. Every module listed is vision; none are claimed as available.
End to end, for print
The vision joins intake, ordering, tracking, production and fulfillment, instead of one more point solution to stitch to the others.
Set up with you, not handed to you
Our team intends to configure CMYK Pro around how your shop already runs, so adoption is not left to a weekend of settings pages.
Powerful software, approachable by design
Designed for print businesses of all sizes, with connected workflows and tailored setup that reflect how your operation works.
04AI design principles
Automation for the work that slows your team down.
In Job 2417, every suggested draft waited for a person. That’s deliberate. These are the rules we’re holding AI to — principles, not a feature list.
- Principle 01
Draft, then decide
AI is intended to prepare the first pass — a reply, a quote, a status note. A person in your shop reviews and sends.
- Principle 02
Inside the job, not beside it
Suggestions should appear where the work happens, with the job's context, rather than in a separate tool you copy from.
- Principle 03
Shop rules come first
Your pricing logic, your minimums, your turnaround promises. Automation should follow the configuration you set together with us.
- Principle 04
Show what it touched
When automation changes something, it should be visible and reversible. Quiet magic is hard to trust on a deadline.
05Hands-on implementation
Powerful software shouldn’t mean complicated setup.
The pricing rules behind Job 2417’s quote draft are yours. Our team intends to configure them with you, along with your statuses and workflow. This is the planned service, not a record of completed deployments.
Step 01
Discover
We learn how jobs really move through your shop — the paperwork, the shortcuts and the exceptions.
Step 02
Configure
Workflows, statuses and pricing logic set up to fit your operation instead of a generic template.
Step 03
Train & launch
Your front office and floor learn the system on their own jobs, not a demo dataset.
Step 04
Improve together
As the platform develops through beta, we refine the setup with you.
How pricing is intended to work
- Monthly subscription tiers for the software.
- A separate, one-time onboarding fee for hands-on setup.
- Tiers, prices and terms are not final and are not published yet.
Requests not openEarly access · preview
Early access isn't open in this preview.
We're preparing for beta and haven't opened requests on this site yet. There is no form here on purpose — nothing you do on this page is collected or stored.
- 01When beta requests open, this section will explain how to apply.
- 02Beta participants will see what is ready and what is still coming.
- 03Availability will vary by capability throughout beta.
06Straight answers
Questions, answered truthfully.
We’d rather tell you what isn’t ready than let a page imply it is.
Not generally. A working platform exists and is in active development, and we are preparing for a beta launch. It is not a generally available product yet.
No claims are being made that they are. The workflow concept illustrates the platform vision. Each capability is still being verified, and beta participants will be told plainly what is ready.
Print businesses of all sizes across the industry — including screen printing, embroidery and apparel decoration, signs and wide-format, and commercial and digital print. From independent shops to large print operations, CMYK Pro is being developed with the industry's varied workflows in mind.
The intended model is a monthly software subscription in tiers, plus a separate onboarding fee for hands-on implementation. Tier names, prices and terms have not been set.
Our team intends to configure workflows, statuses and pricing around how your shop works, and help train your people, rather than leaving setup entirely to you.
Not on this site yet. Requests are not open in this preview, and this page does not collect any information. When beta requests open, the early access section will explain how.
We are not announcing any integrations at this stage. If integrations become available, they will be listed only after they are verified.
Job 2417 · picked up Friday, in the vision