Skip to content

Management software built around your operations,not the other way around

Retyping, chasing, reconciling: your teams should not be doing this by hand. Witify builds the system they work in. Automations take care of the rest.

Talk to an expert

A small team organizing a company’s tasks and data together
For
SMEs, organizations and institutions in Quebec
Technologies
Laravel, Vue, MySQL, AWS
Team
Montreal, across Quebec

01 At a glance

10 years of automating operations

Weekly imports, invoices sent to accounting, scheduled reminders: we build these automations for SMEs, distributors and institutions. They run in their systems every day, often overnight.
  • 2016

    year founded A Montreal team.

  • Over 1,200

    deployments a year Fixes, adjustments and new rules, released at our clients.

  • 21

    files imported every week At HEC Montréal, in 18 steps, under three automatic checks.

  • 20

    published case studies Several show their automations, step by step.

02 When

Where time goes, without anyone noticing

Your processes are unique. Your tools are not. The gap gets filled by hand, every week, in tasks no report ever shows.
An employee’s hands on a keyboard at her desk
  1. The spreadsheet three people edit

    The real list lives in a shared file. Nobody knows which version is right, or who changed the last row.

  2. The approval asleep in an inbox

    A request has been waiting for a signature since Tuesday. The sender keeps following up. The signer has not seen it.

  3. Monday’s file, imported by hand

    Every week, someone opens the supplier’s export, cleans it up and pastes it somewhere else. The day that person is away, nothing happens.

  4. Two programs that do not talk

    Online store sales get retyped into the accounting software. The gaps surface at month-end reconciliation.

  5. The report that comes too late

    The month’s numbers are compiled on the 15th of the next one, once the decision has already been made.

  6. The reminder that depends on someone’s memory

    Following up with a client, renewing a contract, sending the schedule to the teams: if that person forgets, nobody does it.

To connect two applications with a simple flow, a tool like Zapier or Make is often enough. When that is the case, it is what we recommend.

A system earns its place when the logic branches, when an approval takes days, or when an error has to be seen and fixed by someone. Our analysis settles the question, one process at a time.

03 What we automate

The management system, and everything it does on its own

At the centre, the system your teams work in. Around it, the tasks it handles without anyone having to think about them.

01

File imports

Supplier exports, Excel or CSV files: read, checked, then loaded. An invalid row gets flagged, not swallowed.

02

Syncs

Accounting, online store, CRM: customers, invoices and stock move from one tool to the next without retyping.

03

Approvals

Thresholds, delegates and reminders. Everyone sees what is waiting for their signature, and for how long.

04

Generated documents

Invoices, orders, schedules and reports produced as PDF or Excel, then sent to the right people.

05

Notifications

A confirmation to the client, a notice to the approver, an alert to the team when a send fails.

06

Scheduled jobs

Backups, reports, reminders: each job has its time slot and starts without anyone launching it.


Depending on the size of the project

A targeted automation, a central system or a suite that connects every department: the same team handles it, with the same method.

04 At work

Every automation reads step by step

Four automations like the ones running at our clients, each with the screen that tracks it.

Import

Monday’s file, loaded before the team arrives

The system fetches the supplier’s export, checks every row, loads the database and prepares the reports. Three checks watch over every delivery.

HEC Montréal: 21 files every week

Sync

The invoice goes to accounting on its own

Every document created in the system is sent to the accounting software. The record keeps a log of every send.

Distribution MA: the ERP connected to QuickBooks

Approval

Above the threshold, the request waits for the right person

The rule is written as one sentence. The reminder and the hand-off follow, and nobody has to chase anyone.

Scheduled jobs

The week runs, even when nobody thinks about it

Overnight lock, Monday import, Thursday schedule, Friday reminders. When a file is missing, the right person gets an email.

KRSC: two automatic sends every week

05 Method

Understand before automating, validate before coding

Automating a process nobody fully understands only repeats its flaws faster. So every project goes through the same phases, and each one delivers a document or a screen you see and approve.

01 Discovery

We watch the work as it is really done.

Meetings with the people who carry out each process, not only with those who oversee it. Repetitive tasks, retyping and waiting are noted, then ranked by the time they cost.
Fig. 01 Pain points found, ranked by priority

02 Analysis

We trace the path of every piece of data.

For each tool in place, we note what it holds, who feeds it and where information gets copied by hand. Then we decide its fate: connected to the new system, or replaced by it.
Fig. 02 The tools in place and the role of each

03 Data model

A structure that keeps track of everything.

The elements of your processes become tables linked to one another. The automations get their own log too: every run is recorded with its result, so it can be read back.
Fig. 03 The data model and the log of runs

04 Mockups

Your teams approve the screens before development.

The screens where your teams will follow and correct the automations’ work are drawn first. The people who will use them comment on them, and the mockup is adjusted until it works for them.
Fig. 04 A mockup, commented on by its future users

05 Specification

Every automation, described then approved.

Trigger, conditions, exceptions, who gets notified on failure: every automation is described with the checks that prove it works. You approve the document before we start coding.
Fig. 05 A rule, described and approved

06 Development

A delivery every week.

Development moves in one-week sprints, with Sprintify, our AI-assisted code generation, and its ready-made components. Each finished automation reaches staging, where your teams put it to the test with their own files.
Fig. 06 The sprint board

07 Quality

Tests that run again on every change.

Every automation has its automated tests, common cases and edge cases included. They run on every change, after a code review, before anything goes live.
Fig. 07 An update, checked before production

06 Reliability

An automation that fails has to show it

An error will happen one day: an incomplete file, an unknown code, a service that does not answer. What matters is that it stops the work cleanly and that someone knows.
An import stopped at the faulty row, ready to resume
  1. Stop at the faulty row

    The risk
    An import crashes halfway through a file. Nobody knows what went through and what is missing.
    Our choice
    The import stops and names the file, the row and the reason. Once the problem is fixed, it resumes from that row. HEC Montréal’s weekly import works this way.
    The gain
    You fix the row at fault, without starting the whole import over.
  2. One tool holds each piece of data

    The risk
    Two systems each show their own number. Nobody knows which one to trust.
    Our choice
    Each piece of data has a single source tool. At Original Garage Motosport, the system holds the stock and sends it to the online store every 15 minutes, under checks that flag a stalled sync.
    The gain
    One number is right, everywhere.
  3. Every error has an addressee

    The risk
    An automation breaks down on a Friday. Nobody notices before month end.
    Our choice
    An email on every failure, a daily watch and regular checks. Refused sends stay listed, with the message the other software returned.
    The gain
    The problem is known right away, by the person who can fix it.

07 AI

Rules first, AI where judgment is needed

In most automations, a written rule is enough: it can be tested and it does not drift. AI takes over when a document has to be read, or when something has to be sorted that no rule describes well. See our AI integration service.

What a rule does better

  • Compare an amount with a threshold.
  • Calculate a tax, a margin or a due date.
  • Send a reminder after two days without an answer.
  • Give the same result every time, with tests that prove it.

Where AI helps

  • Read an invoice received as a PDF and pull out the useful fields.
  • Sort incoming photos or requests: at OrionFlow, it classifies belongings photographed after a loss.
  • Triage an inbox before a person takes over.

What it does not decide

  • Approving an expense or changing a price.
  • Validating its own work: at OrionFlow, a category suggested below the confidence threshold waits for an assessor.
  • Committing the company: that decision stays with a person.

08 Go-live

A switch-over prepared with your teams

An automation replaces a habit. Before the current way of working is dropped, your teams have seen the system handle their own files.
  1. Data migration Your spreadsheets and the history worth keeping, checked then imported.
  2. Trials with your cases Your key users run their real files through each automation, exceptions included.
  3. Planned switch The manual task stops on an agreed date, away from your busy periods.
  4. Training Each team learns what the system does on its own and what is still theirs to do.
  5. First weeks The first runs are watched closely. Our analysts can come and back your teams up on site.

09 After

A partner who spots what else can be automated

A first automation frees up time, then exposes the next bottleneck. After go-live, we stay at your side to find it, measure what each change brings and advise you on what is worth doing. Day-to-day upkeep is covered by our support and maintenance offer.

01

Time saved, measured

The log of runs shows what the system did on its own. We turn that data into hours recovered, so what comes next is decided on facts.

02

The next bottleneck, found

When one step speeds up, the waiting moves somewhere else. We review your processes with you and propose the next automations, ranked by the time they will save you.

03

A close watch on automation and AI

New AI models, new integrations, new tools on the market: we follow what changes and tell you what applies to your operations, and what can wait.

04

Advice before every decision

Software to connect, a department that grows, an acquisition: we help you weigh the options before you commit, the way a member of your team would.

10 Our work

Automations in service

OrionFlow, built for TSA, has AI sort the photos taken after a loss, then hands each file to the assessors. At HEC Montréal, the weekly import. At the Kent Regional Service Commission, schedules and reminders. Each case study shows the system at work.

View all projects

  • OrionFlow

    Contents claims

    A whole house in photos. AI makes the inventory.

    Custom software

  • HEC Montréal

    Academic research

    Thousands of artists. Measured every week.

    Custom software

  • KRSC Waste Management

    Municipal waste management

    A whole region asks. One commission plans.

    Custom software, Custom ERP

I used to spend my days counting parts and fixing numbers. They automated all of it and I cut the time I spend managing my inventory by 75%. That time now goes back to my customers.

André-Pierre Cloutier Co-owner, Original Garage Motosport

11 Questions

Questions and answers

The questions that come up when a company wants to stop doing a task by hand.

Another question? Write to us at info@witify.io or call 1 800 334 9031.

What is included in management and automation software?

Management software is the system your teams do their daily work in: entering a request, approving an expense, tracking inventory, invoicing a client. Depending on what it covers, it also goes by management system, intranet, platform, ERP, WMS or CRM.

Automation covers everything that system does without being asked: importing a file, sending an invoice to accounting, reminding an approver, producing a report. A project can target a single department. It can also bring HR, sales, operations, inventory, logistics and accounting together in one system.

Do you customize existing software or develop it from scratch?

Many firms implement and configure existing software. Our approach is different: we build custom web software around your processes, without the ceilings of an off-the-shelf product.

We still connect the tools that do their job well, such as your accounting software. If a product on the market already covers the essentials, we tell you.

How long before the system actually runs?

It depends on the scope. Business analysis takes a few weeks to a few months. Development then moves in one-week sprints, so you see parts of the system working well before the full go-live.

We start with the automations that fix your most expensive irritants, so the system pays its way before the project ends.

What if I need a custom platform for my business?

That is exactly what we build. The platform can serve internal management, a client portal or partner access, each with its own permissions. The analysis sets the scope with you before the first screen.

I have been using obsolete software for a long time, can it be modernized?

It depends on the software. If it has an API, we can build bridges and targeted tools that cover its gaps until a lasting solution is in place. In some cases, the source code can be taken over and brought up to current standards.

In others, the software has to be replaced. Data migration and the transition are then planned with you. A technical analysis helps choose the path and set a plan that fits your timeline. See our application modernization service.

I already use software like Quickbooks for my accounting, is that compatible?

Yes. Accounting software that does its job well does not need replacing: we connect it to the new system. The ERP of Distribution MA, for example, creates its own customers, invoices and payments in QuickBooks.

The analysis takes stock of your existing software to decide which tools to keep and connect.

When is a tool like Zapier or Make a better fit than a custom system?

When the flow is simple, the applications involved already have a connector and the volume stays modest. An automation platform then costs less, and your team can change it on its own. In that case, it is what we recommend.

A custom system makes sense when the logic branches, when an approval stretches over several days or when an internal tool has no connector. It also does when volume grows, when data has to stay in your environment or when every failure has to be seen and followed up. Many companies start with a platform to prove the flow. A system can take over later.

Which processes are worth automating first?

The ones that come back often, whose rules are stable and whose data is already digital. Start with the most repeated, most error-prone task. Measure the result, then widen the scope.

During the analysis, we rank your processes by the hours they take and the risk they carry. The expected gain is worked out with you at that stage.

What happens when an automation fails?

It stops where it failed and says why. The right person gets an email, a daily watch makes sure nothing slipped by, and items in error stay listed until they are fixed.

At Distribution MA, a dashboard shows every send to QuickBooks that is stuck. At HEC Montréal, the weekly import resumes from the faulty row once the problem is fixed.

How much does automating a process cost?

The price depends mostly on the number of systems to connect and on how clear the process is, more than on the tool. A targeted automation is often part of a larger project, so it is priced after the analysis.

As a benchmark, most of our SME projects cost between $50,000 and $250,000. Our article on the cost of custom software details what makes the budget vary.

Let’s talk about your operations. Thirty minutes is enough.

Show us the process that costs you the most hours. An expert tells you what can be automated, what needs a system and where to start.

  • A 30-minute call with an expert, not a salesperson
  • A realistic budget estimate, backed by numbers
  • A concrete action plan, whether you work with us or not
Or write to us

Free. No commitment. Reply within 24 hours.

Names and figures shown in the interfaces are examples.