tyntex.Book an audit call ↗
AI automation builds for ops-heavy SMBs

More headcount.
Less busywork.

We build three AI automations into your existing stack in 30 days, so your team stops doing the work AI should. If we do not save you 40 hours a month, we refund $2,500.

Book a 30-min audit call ↗See the 30-day build
No SaaS upsellNo retainer trapCo-founder reply < 24h
In writing, 40 hrs/mo
Tyntex Build, the dealHours-tied
0
Days
From kickoff to three live automations.
0h
Saved/mo
Measured against your baseline, in writing.
0%
Back
Refunded if we miss the number. In the contract.
Build timelineWeek 4, live
MapScopeBuildShipProve
Ops-heavy SMBs×Founder-led service businesses×Agencies running on spreadsheets×Finance teams stuck in Excel×Support inboxes nobody answers×B2B teams shipping by hand×Ops-heavy SMBs×Founder-led service businesses×Agencies running on spreadsheets×Finance teams stuck in Excel×Support inboxes nobody answers×B2B teams shipping by hand×
01 · The premise

Why most AI rollouts
never make it to production.

Ops-heavy SMBs are not short on AI ideas. They are short on shipped automations. Licenses get bought, a workshop happens, and the team goes right back to copy-pasting between tabs, still paying for those leaked hours in headcount.

01

You hired to fix process

Your last three hires mostly copy-paste between systems. Good people, wasted on work AI handles in its sleep.

02

The tools are bought, the work has not changed

ChatGPT licenses, a Zapier bill, and the same people still moving the same data between the same tabs.

03

Every audit ends in a deck

Consultants map it, deck it, and leave. Nothing ships. The hours keep leaking.

04

In-house builds stall at week six

Your best engineer wires up two automations, then a fire pulls them away. The half-built thing sits there for a quarter.

02 · How it works

Four weeks from
first call to three
live automations.

Map the work, scope what is worth building, ship into your stack inside a month. The roadmap is one page, not ninety slides.

01◧Week 1

Map

Two days shadowing your team. We rank your top five workflows by hours leaked per month.

02◇Week 2

Scope

Three workflows make the build list. You sign off on inputs, outputs, and what good looks like.

03◐Week 3

Build

We wire the automations into your existing stack. No new SaaS, no migration, no rollout.

04▤Week 4

Ship

Each automation goes live with one owner on your team. Short Loom, one-page runbook.

05↗Day 30 onwards

Prove

We track hours saved against your baseline for 30 days. Miss 40 a month, the back half is free.

03 · The math

The deal,
in writing.

Every Build is signed against three numbers. They live in your contract, not on a marketing page.

0
Automations
Ranked, scoped, and shipped into your existing tools.
0h
Hours back, monthly
Measured against the baseline we capture in week one.
0%
Back-half refund
Tied to the 40-hour number. Miss it, we refund and you keep the builds.
04 · A way in

The Automation
Audit.

$1,500, one week. A 20-page map of the five workflows worth automating first, ranked by hours leaked, with a build estimate on each. The same brief you would hand any vendor.

“Discovery calls are demos. The Audit is paid work.”
Start the Audit ↗
Tyntex / v.01 · 2026Deliverable
20pagemap

The Automation Audit.

Five workflows, ranked by hours leaked. Yours to keep, whether you hire us or not.

01Two days of shadowing the actual work
02Top 5 workflows ranked by hours leaked
03Build estimate, tool choice, owner per workflow
04What to fix in-house, what to outsource
0530-day build plan if you want one
$1,5001 week
05 · Pricing

Three ways in.

Start with the Audit. Upgrade to the Build when you are ready. Operator keeps it running after.

Audit
$1,500
One week
A 20-page map of the five workflows worth automating first, with a build estimate on each.
  • ✓ Two days of shadowing your team
  • ✓ Top 5 workflows, ranked by hours leaked
  • ✓ Build estimate and tool choice per workflow
  • ✓ Owner suggestion per workflow
  • ✓ A 30-day build plan if you want one
Start the Audit
Most chosen
Build
$5,000
30 days, hours-tied
Three production-ready automations wired into your existing stack, with the 40-hour-a-month guarantee on the back half.
  • ✓ Everything in the Audit
  • ✓ Three automations, built and shipped into your stack
  • ✓ Owner training, runbook, short Loom per build
  • ✓ Baseline capture in week one
  • ✓ 30-day post-handoff tuning
  • ✓ Direct Slack channel with the co-founders
  • ★ 40 hours a month saved, measured in writing. Or back half refunded, builds yours to keep.
Book a 30-min audit call ↗
Operator
$2,500/mo
Ongoing, after a Build
A standing AI engineer on your team. New workflows monthly, the existing ones kept running, models swapped as price-to-performance shifts.
  • ✓ One new automation shipped a month
  • ✓ Monitoring and tuning on the existing three
  • ✓ Model swaps as cost-to-quality changes
  • ✓ Monthly hours-saved report to the founders
  • ✓ Cancel any month, no notice period
Talk to the founders
06 · The co-founders

Three people.
One inbox.

No agency overhead. No junior staff doing the work in the background. The names below are the people building, replying, and shipping.

Hamid Ali Khan
Co-founderHamid Ali Khan
StatusAvailable now
Email[email protected]
LinkedIn↗ in/hamid-ali
Usman Zahid
Co-founderUsman Zahid
StatusAvailable now
Email[email protected]
LinkedIn↗ in/m-usmanzahid
Abdullah Sajid
Co-founderAbdullah Sajid
StatusAvailable now
Email[email protected]
LinkedIn↗ in/abdullahsajidfr

We build AI automations for ops-heavy SMBs, the kind of business where the founder still knows everyone on payroll and the team has quietly lost a quarter of its week to copy-paste work.

Support inboxes filling at the same hour every day. Quotes retyped from PDFs into a CRM. Leads dropping into a spreadsheet nobody wired up. It pays the bills, but it is not what the team was hired for.

A Tyntex Build fixes three of those in 30 days. They land in your stack, your team owns them, and the 40 hours show up on the next ops report. In writing, in the contract.

The three of us study CS at LUMS. Tyntex is small by choice. Three co-founders, no agency layer. The work is ours.

Book a 30-min audit call ↗Company on LinkedIn
07 · Questions

The honest answers.

Six common ones. If yours is not on this list, the co-founders read every inbound at [email protected].

No. We build the automations into your stack and hand them over running. One-page roadmap, working software, no maintenance burden left on you.
Week one, we record the baseline together: who does the work, how long, how often. Day 30 post-launch, we compare. Miss 40 hours a month across the three automations and the back $2,500 is refunded. You keep every build.
Messy, high-volume work is where automations pay back fastest. If the inputs are too inconsistent to automate, we tell you before the contract is signed.
OpenAI, Claude, n8n, Make, Zapier, Python where it fits. The cheapest tool that holds up at your volume. Vendor lock-in is a tax on you, not on us.
Ops-heavy SMBs doing $1M to $20M in revenue. Service businesses, agencies, finance and back-office teams. Founder-led, decision in one room.
Audit: $1,500, one week of paid work. Build: $5,000, half up front, half on delivery. Miss 40 hours a month and the back half is free. The numbers are in the contract.
Start with the Audit

Start with the Audit.
Then decide.

$1,500, one week of paid work, a 20-page map of the workflows worth automating first. Yours to keep, whether you hire us for the Build or not.

Book a 30-min audit call ↗See the 30-day build

Co-founders respond within 24 hours. No discovery deck, no demo theatre.

Replace the busywork. Keep the team.×40 hours a month back, or the back half is free×Replace the busywork. Keep the team.×40 hours a month back, or the back half is free×Replace the busywork. Keep the team.×40 hours a month back, or the back half is free×Replace the busywork. Keep the team.×40 hours a month back, or the back half is free×