Engineering-led AI, automation & business systems · Edmonton, Alberta

Turn manual work into intelligent systems.

RootN finds the repetitive work inside your business (the re-keying, chasing, copying and reporting) and replaces it with the right system: AI, automation, a custom application, a dashboard or simply a better process.

A 30-minute call with the engineer who would build it. Reply within one business day.

Built so far A full operating system for an Edmonton upholstery studio · 60,000+ timesheets through one digital workflow, built as an engineer inside a heavy-civil contractor

Typical pattern The same work, two ways

Today · disconnected

  1. Request arrives by emailInbox
  2. Details retyped into a spreadsheetRetyped
  3. Copied again into the quote templateRetyped
  4. PDF built and emailed by handManual
  5. Report rebuilt from scratch on FridayManual

Five hand-offs, three copies of the same data, and nobody sure which one is current.

Connected · automated

  1. Request arrives by form or emailCaptured once
  2. AI reads it and fills in the recordAI
  3. Quote generated from that recordAutomated
  4. Customer approves onlineSelf-serve
  5. Dashboard updates itselfLive

One record from request to report. People handle the exceptions and the decisions.

A typical pattern, drawn. Every business has its own version.

Real work

Systems built around how real businesses operate.

An upholstery studio, two service brands and a heavy-civil equipment operation. If we can understand their workflows and build around them, we can probably understand yours.

Business system · Website

Sofa Art Upholstery: from paper, texts and PDFs to one operating system

A family-run upholstery studio ran on fillable PDF quotes, spreadsheets, paper work orders and text messages. RootN’s founder designed and built one system around how the shop actually works, from the first inquiry to the follow-up after delivery, alongside a new website.

60+
screens across the staff app, the customer portal and reports
8
staff roles, each seeing what it needs
32
workflow steps tested end to end, inquiry to review request
See the system
Owner dashboard: revenue against collections, unpaid invoices by age and jobs by stage (demo data)Quotes list with sent, viewed, accepted and rejected statuses (demo data)Week schedule with pickups, site visits and production blocks (demo data)A job with its stages, hold points and balance owing (demo data)
Shop floor: Real interface, demo data.
Shop floor. Real interface, demo data.

Real screens from the working application, run on a private copy with its fictional demo data: every customer, amount and date shown is sample data, not a real customer.

How the pieces connect

One connected system instead of five disconnected steps.

Every business is different, but connected operations share the same layers. Choose one to see what happens there, and where we have built it.

Playing through the layers. Choose one to explore it yourself.

01 Customer

The system should make the customer’s part easy: one link to see a quote, choose an option, sign and see the deposit due, without a phone call.

Example In the Sofa Art system, customers open a secure link to view a quote, pick an option and sign.

02 Front door

Requests arrive with the details the next step needs, checked for spam and duplicates, instead of a free-text email someone has to decode.

Example Sofa Art’s system accepts website inquiries through a signed webhook: a customer, a lead and a follow-up task, created in one step.

03 Automation

The repetitive hand-offs (copy this, email that, remind them) run on their own, with alerts when something fails and a manual fallback where it matters.

Example Inside a heavy-civil contractor, a digital form and an automated flow handled 60,000+ timesheets: PDF built, saved and filed with no handling in between.

04 Business system

Customers, quotes, jobs, schedules and invoices in one place, shaped around how you actually operate, with permissions for each role.

Example Sofa Art’s operating system has more than 60 screens and separate views for the owner, office, estimators, the shop floor and drivers.

05 Database

One source of truth, so the history is trustworthy and reports agree with each other. Your data, in a standard database you can export.

Example Every Sofa Art record lives in standard PostgreSQL, and a single command exports a business’s data as JSON and CSV.

06 AI

Used where plain rules run out: reading varied documents and emails, pulling out the fields, drafting replies for a person to approve, answering questions about your own data.

Example Illustrative: a supplier email becomes a structured purchase record, and anything uncertain goes to a person to check.

07 Dashboards, actions, alerts

What is late, what is owed, what needs a decision, as a dashboard, a scheduled report or a nudge to the person who can act on it.

Example Sofa Art’s dashboard shows revenue against collections, unpaid invoices by age and jobs by workflow stage.

What we build

Outcomes first. The technology follows.

Sometimes the answer is AI. Sometimes it is a simple automation, a custom application, a dashboard or a better process. We recommend what fits, and say so when the answer is “not yet”.

01 AI & document intelligence Read documents and email, extract what matters, route it, draft the reply, answer questions about your own data. Language models in your approved services · extraction and classification · review queues · retrieval over your documents Information that arrives as text becomes structured work, without someone retyping it. 02 Workflow automation The copying, chasing, filing and reminding that happens between steps, done by software. Power Automate · scheduled flows · generated PDFs · email and Teams notifications · desktop automation as a bridge Fewer hand-offs, fewer errors, and processes that don’t depend on one person’s memory. 03 Custom business systems Applications built around how your business actually runs, when spreadsheets and off-the-shelf tools no longer fit. Web applications · PostgreSQL · role-based access · customer portals · PDF documents · audit history One record from first inquiry to final invoice, with every step visible. 04 Data, dashboards & reporting Reports that assemble themselves and dashboards built around the decisions people actually make. Power BI · scheduled data pulls · Python (pandas) · agreed KPI definitions · Excel where it belongs Numbers people trust, on time, without someone rebuilding them every week. 05 Systems integration Connect your website, forms, email, applications and databases so information is entered once. REST APIs · signed webhooks · scheduled file exchange · validation and retries · change logs Systems that agree with each other, and a record of everything that moved between them. 06 Websites & customer experience A credible brand and website that act as the front door to your operation, not a brochure. Fast static sites · structured quote forms · spam protection · brand marks · intake into your system Customers can find you, understand you and ask for a quote in a way your team can act on.

Also: Equipment & maintenance analytics

Practical AI

AI that does real work inside your systems.

Most business information still arrives as text: emails, PDFs, forms, notes. AI can read it, pull out what matters and turn it into structured work, with a person checking anything uncertain.

  • Turn emails into structured work
  • Extract data from documents
  • Route requests by what they say
  • Draft replies and documents
  • Answer questions about your own knowledge
What AI can do in your business

Arrives as text

Supplier · Order update

Hi, confirming your order of 3 rolls of the charcoal performance fabric (54").

Two rolls ship Thursday; the third is backordered about two weeks.

Invoice 4471 to follow. Please quote the job reference on payment.

Becomes structured work

Type
Order confirmation
Item
Charcoal performance fabric, 54"
Quantity
3 rolls
Shipping
2 rolls Thursday, 1 backordered (~2 weeks)
Invoice
4471 (to follow)
  • AutomaticMaterial record updated
  • AutomaticJob flagged: waiting for material
  • A person approvesCustomer delay message drafted
Illustrative example with invented content. The system it writes to would be yours.

How we think

Understand the business first. Build the right technology second.

We don’t show up and start writing code. We find out how the work really runs, remove what shouldn’t exist, then build only what pays for itself.

  1. 01

    Understand

    How the work really runs today, who touches it, and what it costs.

  2. 02

    Map

    Every hand-off, copy and wait, drawn out and timed.

  3. 03

    Simplify

    Remove the steps that shouldn’t exist before automating anything.

  4. 04

    Build

    The right tool for each step: a rule, a flow, an application, AI or nothing at all.

  5. 05

    Measure

    The same measure before and after, so the result is a number, not an opinion.

  6. 06

    Improve

    Hand it over documented, then tune it as the business changes.

How engagements work, and how we handle your IT and data

Across industries

Different businesses. The same patterns.

The industry changes the vocabulary, not the problem. These are the patterns we see most.

Request → quote → job → invoice

Upholstery and repair shops, contractors, home and field services, fabrication

One system from first inquiry to paid invoice, with online approval and a job board

Field paperwork → office

Construction crews, cleaning and maintenance teams, inspectors, drivers

Phone forms, generated PDFs, automatic filing and approvals

Documents in → data out

Professional services, property management, logistics, suppliers and accounts payable

AI extraction with a review queue, routing by content, records created in your system

Scattered data → one report

Manufacturing, equipment fleets, multi-site operations, growing companies

Scheduled data pulls, agreed definitions and dashboards that refresh themselves

Customer front door

Local and growing service businesses

A credible brand and website with structured quote requests that feed the next step

Where these patterns show up

Where the approach comes from

Shaped where bad processes have real consequences.

RootN’s approach was formed inside a heavy-civil contractor’s equipment operation, where disconnected data, crews, machines and maintenance decisions cost real money. We bring the same systems thinking to businesses well outside heavy industry.

Read the five field notes

Systems built by RootN’s founder inside a Western Canadian heavy-civil contractor’s equipment operation. The employer and its systems are not named.

We find inefficient work inside businesses and build technology that eliminates, automates, connects or improves it.

AlaaEldin Hebiba, P.Eng.

Who you’ll work with

The engineer who designs it is the one who builds it.

RootN’s founder builds the systems on this site: from automations inside a heavy-civil operation to a full operating system for a local business.

There is no hand-off from a salesperson to a junior developer. The first call, the diagnostic and the build are with the same person, who understands both the operation and the code.

About RootN

Before you book

The questions people ask first.

We’re not an industrial business. Is RootN for us?

Yes. The problems are the same across industries: information typed twice, approvals chased by email, reports rebuilt by hand. The Sofa Art system was built for an upholstery studio. The industrial background is where the approach was shaped, not a limit on who we work with.

Do we need AI?

Not always. We start with the work, not the technology. Sometimes the answer is AI, sometimes a simple automation, a custom application, a dashboard or a better process.

RootN is one engineer. What happens if you’re unavailable?

The work is designed not to depend on us. It is built in your environment wherever possible, under service accounts rather than a person’s login, documented as we go, with a manual fallback for anything payroll- or billing-critical. You own the code, flows and data, so your team or another developer can pick it up. And you always deal directly with the engineer who builds it.

Who owns what you build?

You do: code, flows, data and documentation. Nothing is locked to RootN.

How do you handle our data?

We work in your systems with service accounts, use a separate MFA-protected account removed at handover, keep secrets in your vault, sign NDAs and complete security questionnaires. AI data use is agreed in writing first.

What does it cost to start?

The first call is free. A diagnostic is a fixed price agreed before we start, from $1,500, and it is credited to the build if you go ahead within 60 days.

Next step

Show us what’s slowing your business down.

Bring one process that eats time. In 30 minutes we’ll look at how it runs today, what it costs, and whether AI, automation or a better process would fix it. You leave with one concrete next step, even if it isn’t with us.

Request a 30-minute call

With the engineer who would do the work. Reply within one business day.

contact@rootn.ca · +1 (825) 436-3300