We find the work eating your week, and engineer it out.

Codision is a Toronto AI engineering studio. We measure what a manual workflow costs you in hours and dollars, then build the production system that removes it.

Describe your workflow See how we measure
Illustrative exampleNew client file at a 30-person immigration practice
Swimlane diagram of the workflow across four lanes: email inbox, your team, spreadsheet, case system.
    Time spent per week
    hours14.5 hours
    Cost per year
    $36,192

    676 hours a year back to the team

    Manual stepHandled by the systemBottleneck

    Cost = hours × $48/h (wage plus benefits and overhead) × 52 weeks. Example figures for one intake workflow, not client data.

    The expensive work is the work nobody sees.

    It’s spread across everyone’s week: ten minutes re-typing a form here, an afternoon reconciling spreadsheets there. Nobody owns it, so nobody counts it.

    We count it. Then we start with the single workflow that costs you the most.

    Re-typing data from PDFs and emails into systemsIntake forms, IDs, invoices, applications

    9.5 hours a week, the workflow to start with

    Chasing missing documents and signaturesReminder emails, follow-up calls

    6.0 hours a week

    Reconciling spreadsheets against each otherTrackers, exports, month-end checks

    5.0 hours a week

    Copying updates between disconnected toolsInbox to CRM, CRM to accounting

    4.5 hours a week

    Building the same weekly report by handStatus updates, client summaries

    3.0 hours a week
    Per week28.0 h Per year, at $48/h$69,888 Illustrative example: the same immigration practice as above, across all of its manual work (28 h a week). The intake workflow mapped above is one part of it, at 14.5 h a week and $36,192 a year. Your numbers come out of the assessment.

    What your team sees instead.

    No more re-typing. The system reads the documents, fills the fields and drafts the reminders. Your people do the part that needs judgment: check the flagged field, then approve.

    You stay in the loop on purpose. The system removes the typing, not the accountability.

    Review queueIllustrative example
    • Client file 1Ready to approve12 documents in, all 40 fields filled
    • Client file 21 field to check12 documents in, 39 of 40 fields filled
    • Client file 3Waiting on client8 of 12 documents in, reminder email drafted

    Client file 2: fields read from the documents

    Full name
    Sample Client
    Passport, page 2
    Passport number
    AB123456
    Passport, page 2
    Passport expiry
    2027-03-14
    Low confidence: check against the scan
    Employer
    Example Corp.
    Offer letter
    Filled by the system39 of 40 Left for a person to check1 Illustrative example: what a review screen could look like for the intake workflow above. Names and values are made up. The real screen is designed around your documents and tools.

    Six steps, measured at both ends.

    We don’t start with technology. We start with the bottleneck and a number, and we finish with the same number, smaller.

    1. Bottleneck

      Sit with the people doing the work and map the workflow that costs the most.

      Workflow map

    2. Quantify

      Put hours and dollars on it, so you know what fixing it is worth before anything is built.

      Cost baseline

    3. Design

      Decide what the system does, where your team stays in the loop, and what it plugs into.

      System design

    4. Build

      Engineer it against your real documents, inboxes and tools, not a demo dataset.

      Working system

    5. Deploy

      Put it into production with your team, alongside the tools they already use.

      Live in production

    6. Measure

      Compare against the baseline. The result is reported in the same hours and dollars.

      Before / after report

    If the numbers say a workflow isn’t worth automating, we’ll say so, and you keep the map and the baseline either way. That’s why we quantify first.

    What Codision is, and is not

    • A software agency.
    • An AI consultancy.
    • Staff augmentation.
    • An engineering studio that removes manual work.

    Agencies sell hours of building. Consultancies sell recommendations. Staff augmentation sells people.

    You talk to the engineer who builds it.

    I map your workflow and build the system myself, and when something breaks, I’m the one you call. There’s no account manager in between and no hand-off from a sales team to a delivery team.

    I’ve been building software since 2009. Most of that time went into the unglamorous part: getting changes into production without breaking what already works. I’ve also worked directly with businesses as a freelance developer.

    Edegilson Sousa · Founder, Codision · Toronto

    Background on LinkedIn

    Your first one to two weeks

    1. I sit with the people who do the workWe look at their real documents and inboxes.
    2. I map the workflow and put a cost on itHours and dollars, before anything is built.
    3. I tell you plainly if it’s worth automatingYou keep the map either way.

    Start small. Prove it in production.

    Four engagements, each one earning the next. Scope and price are set after we understand the workflow.

    Workflow Assessment

    1 to 2 weeks

    We map one area of your operations, find the bottleneck, and put a cost on it.

    You get: the workflow map, the cost baseline, and a recommendation you can act on with or without us.

    Automation Pilot

    4 to 6 weeks

    One workflow, taken all the way to production and measured against the baseline.

    You get: a running system your team uses every day, and the before / after numbers.

    Production AI System

    Scoped per engagement

    Several workflows and systems connected, once the pilot has proven the approach.

    You get: multi-system automation across the processes that matter most.

    Managed AI Engineering

    Monthly

    We keep what we built running, monitor it, and keep improving it as your business changes.

    You get: maintenance, monitoring, and a steady list of improvements.

    Most engagements should start with an assessment. If you already know your bottleneck, go straight to a pilot.

    Start with an assessment

    Built for teams that run on documents, inboxes and spreadsheets.

    • Canadian companies with 20 to 500 employees
    • No in-house engineers, and no plans to hire them for this
    • Work that moves through PDFs, email, spreadsheets and tools that don’t talk to each other

    • Immigration and legal

      Client intake, document collection and checking, form preparation, file status updates.

    • Accounting

      Chasing client documents, bookkeeping entry, reconciliations at month-end.

    • Insurance

      Claims intake, policy document review, re-keying between carrier and broker systems.

    • Property management

      Tenant requests, lease administration, invoice processing.

    • Logistics

      Bills of lading, dispatch updates, proof-of-delivery paperwork.

    Questions operators ask first.

    Something else on your mind? Put it in the form below.

    Do we need anyone technical on our side?
    No. We need the people who do the work today, for a few conversations and to review what we build. We handle the engineering, the deployment and, if you want, the upkeep.
    Do we have to replace the tools we use?
    Usually not. The goal is to remove the manual steps between the tools you already have, not to move you onto new ones.
    What does the assessment actually produce?
    A map of the workflow, a cost baseline in hours and dollars, and a recommendation: which part to automate first, what it’s worth, and what a pilot would involve. It’s yours whether or not we build anything.
    How do we know it worked?
    We measure the same workflow after deployment, in the same hours and dollars as the baseline. That comparison is part of the engagement, not an optional extra.
    How much does it cost?
    It depends on the workflow, so we don’t publish prices. Tell us what you’re dealing with and we’ll give you a straight answer on scope and cost before any work starts.

    Describe the workflow that eats your week.

    1. Tell us what happens todayA few sentences is enough: what comes in, who touches it, where it ends up.
    2. We read it and reply personally within one business dayWith questions, or with a first view on whether it’s worth measuring.
    3. If it is, we map it togetherThat’s where the assessment starts.

    Rather talk it through? Book a 20-minute call, or email hello@codision.com.

    Please add your name.
    Please enter an email address we can reply to.
    Please describe the workflow, even briefly.
    We only use this to reply to you. It goes straight to our inbox and never onto a mailing list. Privacy
    Describe your workflow