InkIQ
Sign in Book a demo

Solutions — By function

Every seat in
the building.

The same brain, doing a different job depending on who's sitting in front of it. Here's what changes for each team on the day you switch it on.

Book a demo → Browse by industry

Eight functions

Nobody buys software.
They buy their day back.

An ERP is sold to the owner and lived in by everyone else. These are the eight jobs InkIQ actually changes.

01 / Function

Owners & leadership

Knowing where the money went without asking four people.

 02 / Function

Sales

Quoting faster, following up assuredly, never losing a lead.

 03 / Function

Customer service

A queue that empties itself, on the phone and in the inbox.

 04 / Function

Order entry

The retyping job that shouldn't exist any more.

 05 / Function

Art & production

Files, mockups, approvals and a schedule on real machines.

 06 / Function

Purchasing

What to buy, from whom, and what to send outside.

 07 / Function

Accounting

Invoicing, A/R, A/P and the true cost of every job.

 08 / Function

Workforce & HR

Hours, shifts, PTO and payroll, off the whiteboard.

01 — Owners & leadership

You find out what
happened in April, in May.

Most owners run on a feeling and a bank balance. The real numbers — which jobs actually made money, which customer is quietly shrinking, what's sitting unpaid — live in four systems and two people's heads, and pulling them together takes a week you don't have.

  • —A dashboard you configure per person, so the owner, the sales lead and the production manager each see their own numbers
  • —A written brief in your inbox every morning, in plain English, in the format you asked for
  • —Ask Reggie anything about your own data and get the answer, not a report to go build
  • —Margin visible per job, per customer and per imprint method, costed from the actual work
  • —A/R aging and what's overdue, without opening the accounting package

The point isn't more reporting. It's not having to ask anyone.

Morning brief · 07:00
42
Open orders
$186k
In production
31%
Avg margin
$24k
Over 60 days
Quotes waiting on a replyfollow-ups already sent14
Jobs at risk this weekart not approved3
Lowest margin joborder 4471 · 9%Review

Written by Reggie, sent as email, and answerable — reply and ask why.

02 — Sales

Your best closer spends
the day typing.

The person who's good at winning work is instead collecting quantities, chasing artwork and rebuilding the same quote for the fourth time. Meanwhile the leads that went quiet three weeks ago are still sitting there, because nobody owns the follow-up.

  • —Quotes drafted from the enquiry itself, priced against your tables, ready to review rather than build
  • —A pipeline with stages and automations, so nothing sits untouched because someone forgot
  • —Follow-ups that fire on your schedule and cancel themselves the moment the customer replies
  • —Segments and campaigns that go to the customers a message actually makes sense for
  • —Cold outreach with human-sounding sequences — a full-time prospecting team for the cost of none
  • —Branded catalogue presentations built from your own products, in minutes
Pipeline · this week
New enquiriesquoted automatically28
Awaiting customerfollow-up 2 of 3 sent19
No reply, 14 daysmoved to nurture7
Wonconverted to orders11
Median time to quote6 minutes

Nothing in this list is waiting on someone remembering to chase it.

03 — Customer service

The same question,
a thousand ways.

"Where's my order?" "Did you get the artwork?" "Can I still change the sizes?" Each one is a lookup and a two-line reply, and there are hundreds a week. Your team isn't solving problems, it's reading them out of a screen.

  • —One inbox where every thread files itself against the customer and the order
  • —Status, tracking, artwork and change requests answered from live data, not a knowledge base someone maintains
  • —Voice answers the phone around the clock, from the same brain, and transfers warm when a person is needed
  • —A customer portal, so the routine questions never become messages at all
  • —Anything with a decision in it — a claim, a credit, an exception — escalates with the context attached
  • —You choose the rope: draft only, auto-send the routine, or fully autonomous
Queue · today
Order status
Artwork
Changes
Claims

Lookups collapse. Claims barely move — those are judgement calls, and they should still reach a person.

04 — Order entry

A job nobody
should still have.

Purchase orders arrive as PDFs, spreadsheets, portal exports and photographs of paperwork, and somebody keys them in line by line at the busiest hour of the day. It's the most error-prone work in the building and the least interesting.

  • —POs read from any format — line items, SKUs, colourways, size matrices, dates, terms and PO number
  • —Size-and-colour grids read as a grid, not flattened into a total
  • —Free-text products matched to your catalogue and your preferred vendor for that item
  • —You set what a complete request looks like; anything missing gets chased automatically
  • —Order entry becomes review: nine lines confirmed, one flagged, thirty seconds of attention

Every attachment gets opened and read, in every format — including the ones that are photographs of paper.

PO 88214.pdf · read
Line items10 of 10 matched
Size matrixS 24 · M 60 · L 60 · XL 36 · 2XL 12
In-hands18 Sep
TermsNet 30
Line 7two plausible productsConfirm

It flags the ambiguous line rather than picking one and hoping.

05 — Art & production

The file is wrong and
you find out on press.

Artwork arrives in whatever the customer had. Somebody opens it, counts colours, guesses a stitch count, remakes it at the right size, builds a mockup, chases an approval — and the schedule is a whiteboard that doesn't know which press can run the job.

  • —Every file opened and analysed — distinct colours, stitch estimate at the requested sew width, resolution checked against production
  • —Mockups generated on the real garment, true to size from the supplier's own size chart
  • —Imprint files tagged and searchable, so last year's job is findable this year
  • —Proof approvals as a workflow with reminders, versions and a dated decision
  • —Scheduling onto your actual stations and equipment, not generic work centres
Artwork · customer_logo_FINAL.ai
PlacementLeft Chest
Fabric Type270 GSM Fleece
ResolutionHolds at 4 in
Customer said"two-colour logo"5 colours
Stitch estimate7,400 at 3.5 in
ScheduledPress 2 · Thu 06:00

The colour count is caught before it becomes a quote, not after it becomes a screen.

06 — Purchasing

Ordering blanks
from memory.

Someone checks stock across three supplier sites, picks a vendor from habit, raises a PO in a spreadsheet, and finds out on Thursday that half the size run is backordered. When capacity is tight, deciding what goes outside is another set of phone calls.

  • —Purchase orders raised against the order that needs them, not typed fresh
  • —Products resolved to your preferred vendor for that item, with live catalogue data behind it
  • —Reorder points tracked on consumables, so you order before a cold snap rather than during one
  • —Outsource partners held against the imprint methods they actually run, for overflow routing when capacity is exceeded
  • —What's on order, what's landed and what's late, visible against the job waiting on it
Purchasing · order 4471
Preferred vendormatched from the product recordSet
PO raised192 units
2XL × 12backordered 9 daysSplit
Capacity, week 38embroidery over by 3,100 st/hrRoute out
Outsource partnerruns embroidery · 4-day turn

The overflow decision surfaces while the date is still achievable.

07 — Accounting

You know the revenue.
You don't know the margin.

Invoicing lives in one system, costs live in another, and job profitability is a spreadsheet somebody rebuilds at quarter end. By the time you know a customer is unprofitable, you've run their work for a year.

  • —Invoices raised from the order, with payment links, rather than retyped into the accounting package
  • —A/R aging visible as a live list, with reminders that go out on their own
  • —Accounts payable, expenses and budgets in the same place as the work that caused them
  • —Job costing computed from the actual cost lines on each imprint, not a blended labour rate
  • —QuickBooks export, so your bookkeeper's process doesn't change
Job costing · order 4471
Invoiced$4,860
Blanks$2,190
Screens & set-up$340
Run cost$780
Outsourced embroidery$610
Margin$940 · 19%

Costed from the imprint's own cost lines, so the number survives being questioned.

08 — Workforce & HR

Hours on paper,
shifts on a whiteboard.

Somebody adds up handwritten times on Monday morning. Time-off requests live in text messages. Nobody can say what a job cost in labour because nobody knows who was on it, and the schedule that says who's in is a photograph on someone's phone.

  • —Clock in and out on the floor, with timesheets and approvals instead of arithmetic
  • —Shifts scheduled against your real stations, so the rota matches what's actually running
  • —PTO requested, approved and tracked in one place, not in a text thread
  • —HR profiles, documents and activity kept per employee
  • —Payroll export at the end of the period, from hours that were recorded rather than remembered

Shop-floor time-clock users aren't charged as full seats.

Week 38 · timesheets
Hours recorded14 staff · clocked on the floor521.5
Awaiting approval2 with missing punches2
PTO bookednext 30 days3
Press 2, Thursdayscheduled, one operator shortGap
Payroll exportReady

One system

Eight jobs, one record
of the work.

The reason this works is that none of it is eight products. It's one job record that everybody's seat looks at from a different angle — which is why nothing gets retyped between them.

Book a demo → See the ERP

Watch it do the job.

Send us one real enquiry — the email, the purchase order, the artwork, the messy bits — and we'll run it through the agents in the first ten minutes of the call. That's a faster argument than anything we could write here.

Book a demo → See plans