Record it once. We build the automation in 72 hours — tested on your exact portals, reviewed by an engineer, running in production. Your team keeps every decision. Type-2 keeps the repetition.
Reads an Excel list of container numbers, logs into ANL/MSC/Maersk portals, downloads documents, and dispatches to clients via Outlook. 19 jobs running in parallel. Every email reviewed before it sends.
ANL · MSC · Maersk — live production. Same portals, same credentials, same clients. Timestamps are real.
* tested production workflows onlyEngineer-reviewed before the first run. That's why it holds.
From one trigger. Scale doesn't require new recordings.
19 emails in the queue. Every one reviewed before it sent. Your team decides — the automation waits.
Screen visible? We automate it. Legacy ERP included.
If something unexpected happens, the job stops and flags it — it doesn't guess and keep going. Your team decides what happens next.
How it works
A workflow tested on your exact environment before it runs once.
Open the agent trainer and do the workflow on your screen — logging into portals, filling fields, downloading documents, sending emails. The recorder captures every click, every keystroke, every scroll, with a screenshot at each moment. No scripting. No technical setup. When you stop recording, your part is done.
30 minutes of your time. Nothing else required from your team.
Every action you took — captured with exact coordinates, values, and context — is used by the system to generate a structured workflow template. Every step mapped. Every decision point identified. The system reads your screen the way a person does: understanding what each element is, not just where it sits. That's what makes it resilient when portals update their UI.
Most automation tools are black boxes. Before our system builds anything, you can see exactly what it captured — every click, every value, every screen state. If something looks wrong, you catch it here, before it runs.
The system generates a capable template. Our engineer then validates it against your exact environment before it runs — that's the quality gate.
Our engineer takes the system-generated template, tests it against your exact environment, handles edge cases, adds error recovery, and validates it end to end. This is not a review in name only — it's a run against your actual portals, your actual credentials, your actual data.
What gets deployed is not what the system generated — it's what survived an engineer's hands-on review of it.
This is why the completion rate is 92%+* — not 60%. The system gets you there fast. The engineer gets you there reliably.
19 emails queued. Nothing sent. Every one reviewed before dispatch. You saw this in the demo above — that's not a feature flag, it's the architecture.
Jobs dispatch to whatever machine is available. Proven live: 19 shipments across 3 carrier portals running in parallel.
Auto-generated prompts for every LLM step. You set the model, its flexibility, and exactly which decisions it can make. Our engineers refine these during the build review. The LLM does precisely what you authorised — nothing more.
Execution runs on your machine by default. Full local deployment — zero data leaves your environment — is available for enterprises that require it. Every data routing decision is deliberate and auditable.
Decision trees, approval thresholds, pricing rules, routing logic — configured during the build, runs inside every job.
APIs your team already uses are the preferred path — cleaner and more reliable than screen automation where one exists.
Your agents reason and decide — but stop when there's no API. Type-2 is the execution layer that carries the decision through to the screen.
Carrier portals, supplier portals, legacy ERPs, Outlook, Excel. Semantic recognition — not pixel coordinates.
All capabilities ship in production — not demos, not roadmap items.
Workflows we've built or scoped
If your team does this manually, we've probably seen it.
Not the right fit if Zapier already solves it.
Most automation vendors show you a multiplied percentage. We show you the actual labor hours, the actual hourly rate, and the actual monthly cost — then compare it to what Type-2 costs. You do the math.
Adjust the inputs. The math updates live. Type-2 estimate is based on typical single-workflow pricing.
Type-2 estimate is illustrative — setup and monthly costs are scoped individually on the workflow call.
These are labor-cost estimates, not guaranteed savings. Actual numbers depend on your workflow, team size, and what people do with freed time. We're not in the business of inflating ROI claims — that's why we show you the arithmetic instead.
Every deployment is priced individually — because every workflow is different. You'll know the exact number before you commit to anything.
Four commitments. Every workflow. No negotiation.
Every click path, every portal, built for your exact environment. If it doesn't work on your machine, we rebuild it.
Not a staging environment, not a demo account — your actual portals. We don't ship until it passes.
Others quote 6–12 weeks. We quote 72 hours. No config on your end. No debugging. You click Run.
Portals update. ERPs push patches. First 90 days, if it ran before and doesn't now — we fix it. No ticket, no charge.
Three variables. We tell you which bucket your workflow falls into before you get on a call.
You don't need to know which category you're in before the call. That's what the pre-call assessment is for.
Four steps. You're the subject of every one.
Describe your workflow in plain English — what it does, how often, which systems it touches. No technical knowledge required.
Complexity tier, systems assessment, and whether we think it's a fit. You get this before any call — no call required to get a verdict.
Not a range — a number. Setup cost, monthly estimate, maintenance terms — all confirmed before the call ends.
You have everything you need to decide. No follow-up if you say no. No charge until you say yes.
Monthly usage scales with how many jobs you run and which tools you connect. LLM and external API costs pass through at cost — no markup. You choose which models you use; we tell you what they add before you commit. Your monthly estimate is confirmed on the scoping call alongside the setup fee.
After the included 90-day maintenance window, ongoing maintenance is billed at a flat hourly rate you'll know upfront. Most UI updates take under an hour. Major scope changes — new steps, new systems — are quoted separately, and we'll always tell you the difference before doing any work.
7 workflows. Production-deployed by end of June. Recording to production in 72 hours.
Pre-call assessment included — no call required to get a complexity verdict.
Submit a 2-minute application. You'll receive a pre-call assessment within 24 hours — whether it's a fit or not.
Questions
Real. The 19 shipments are real container numbers. The ANL, MSC, and Maersk portals are live production portals. The emails dispatched to real clients. Nothing was staged, scripted, or run on a test environment.
The sections labelled 7× are compressed — we told you that. Everything else ran at normal human speed, unedited. What you watched is what your team would see running on a Tuesday morning.
Most automation tools work by connecting to software through APIs — structured data pipelines that developers build. When there's no API (and most carrier portals, legacy ERPs, and internal tools don't have one), those tools stop. Your team goes back to doing it manually.
Type-2 works the way a person works — by navigating the screen. No API required. If someone on your team can log in and do the workflow, we can automate it. That's the gap we fill — not a better version of Zapier, but a different category entirely.
The second reason automations break is that nobody owns them after launch. We include 90 days of maintenance — when the portal updates its layout and something changes, we fix it. That's not an upsell. It's in every deployment.
Your part is about 30 minutes. One person on your team does the workflow on their screen while our recorder captures it — exactly as they do it normally. No scripting, no technical knowledge, no preparation required.
After that, we take over. Our engineers build the automation, test it on your exact environment, and deploy it. The next time your team touches it is to click Run — and review the jobs that need a human decision before they execute.
The automation doesn't crash — it stops safely and flags the problem. If a document is missing, a portal behaves unexpectedly, or any step falls outside what the automation was built to handle, that job pauses and goes into a review queue. The rest of the jobs keep running.
Your team sees exactly what happened and handles that one manually. Nothing gets silently wrong — every exception is visible, labelled, and waiting for a human decision. You saw this in the demo: the output tracker at the end shows completed jobs and flagged ones separately.
Your data stays on your machine. The automation runs locally on your Windows desktop — your credentials, your documents, your portal sessions never leave your environment and don't pass through our servers.
During the build, our engineers see the structure of your workflow — which steps happen in which order — not the data flowing through it. We don't store outputs. We don't have access to your portals after deployment. For teams with stricter requirements, full local deployment is available where there is zero external connection of any kind.
You are, at every step that matters. Any action that has a consequence — an email sent, a form submitted, a document filed — goes into a human review queue before it executes. Your team sees what the automation is about to do and approves it. Nothing sensitive happens without a human seeing it first.
The automation handles the repetitive navigation, data entry, and retrieval. Your team handles every decision. That boundary is not configurable by accident — it's the architecture. The demo shows this clearly: 19 emails queued, nothing sent, waiting for a human to review each one.
From your recording session to a working automation in production: 72 hours. Not a pilot, not a prototype — a working automation, tested on your exact environment by an engineer, ready to run.
Pricing has two parts: a one-time setup fee and a monthly usage cost. Both are scoped to your workflow — the complexity, the systems involved, and what you want connected. You get a fixed quote on a 20-minute call before you pay anything. We assess your workflow, tell you the exact number, and you decide. If it's not a fit, we tell you on the call — no charge.
The honest answer: Type-2 is built for workflows that are repetitive, screen-based, and happen on software that has no API or integration support. If your team does the same multi-step process daily — navigating portals, copying data between systems, sending templated emails — and no existing tool automates it, that's our territory.
It's not the right fit if Zapier or Make already solves your problem — those tools cost a fraction of what we do and you should use them. It's also not right if you're Mac-only (we're Windows for now), or if your workflow requires sub-second real-time execution. If you're not sure, describe your workflow in two sentences and send it to founder@type2.io — we'll tell you within 24 hours whether it's a fit, no call required.
Most automation tools locate elements by where they are on screen — pixel coordinates, CSS selectors, or fixed positions. When a portal updates and a button moves two inches to the left, the automation breaks because it's looking at a location, not an element.
Our system understands what each element is, not just where it sits — the same way a person reads a page. When ANL updated its portal layout last year, the automation kept running because it recognised "the download button for this shipment" rather than "the button at position 847, 392." This is what's included in the 90-day maintenance window — and why most updates take under an hour to address when they do break.
If your team does a repetitive workflow that no integration tool can automate — record it once and send it to us. We will tell you in 24 hours whether we can automate it, what it takes, and what it costs.