SEC/D0 · Overview

Data extraction, pipelines and reporting.

The information you need is already somewhere: in PDFs, inboxes, vendor portals, spreadsheets and the systems themselves. Somebody reads it in one place and types it into another. We build what reads it, checks it, moves it where it belongs and reports it in numbers that agree.

  • SYS/01
    PDFs & scans
    Read, not retyped
  • SYS/02
    Email
    Orders and invoices in
  • SYS/03
    Vendor portals
    Pulled on a schedule
  • SYS/04
    Spreadsheets
    Brought into the system
  • SYS/05
    Systems of record
    Where it belongs
  • SYS/06
    Reports
    Numbers that agree

SEC/D1 · Coverage

Where the data comes from, and where it goes

Sources
PDFs and scanned documents · email inboxes · supplier and vendor portals · public websites · spreadsheets · APIs
Destinations
NetSuite · Epicor · Sage Intacct · QuickBooks · Salesforce · HubSpot · SQL Server · Postgres · Snowflake · BigQuery · Power BI · Looker Studio · Google Sheets

SEC/D2 · Symptoms

Where the retyping happens

  • Invoices and packing slips keyed by hand from PDFs
  • A supplier sends a new price list and someone retypes it
  • The weekly report is assembled from four exports and a spreadsheet
  • Competitor pricing or market data is gathered by someone browsing websites
  • Years of history are stuck in a system you are about to leave
  • Two reports, two answers, and a meeting to decide which one is right

SEC/D3 · Outcome

Read once, right everywhere

Today Afterward
TodaySomeone keys invoices from PDFs every morning. AfterwardInvoices are read on arrival, and only the exceptions reach a person.
TodayThe weekly report is four exports and a spreadsheet. AfterwardThe report reads from one place and is ready Monday.
TodayTwo reports, two answers. AfterwardOne number, traceable to its source.

Documents are read when they arrive, and the fields land in the system that needs them. The ones the system isn't sure about go to a person with the document beside the record, so the exceptions get checked and everything else just moves.

Supplier, pricing and market data show up on a schedule instead of on someone's to-do list. The reports read from one place, so they agree with each other and with the systems underneath them.

SEC/D4 · Scope

What we build

Document extraction.

Invoices, purchase orders, statements, packing slips and forms read from PDF and email, validated, and written to AP, inventory or the CRM. Exceptions routed to a person.

Data from websites and vendor portals.

Pricing, catalogs, availability and listings collected on a schedule and delivered clean.

Pipelines.

Data moving between systems on a schedule or the moment something changes.

Migration.

Out of the old system and into the new one, cleaned, deduplicated and reconciled before cutover.

One place to report from.

A warehouse or reporting database the dashboards read from, so every report starts from the same numbers.

Cleanup and enrichment.

Duplicates merged, formats standardized, missing fields filled.

SEC/D5 · Method

How an engagement runs

  1. STEP/01

    Map

    We learn how the business actually runs: what it sells, what it runs on, and where the work gets carried by hand. One storefront or six systems of record, the map comes first.

  2. STEP/02

    Design

    The system is designed around your operation: what gets built, what gets connected, what it looks like, and in what order. A fixed scope and a fixed price.

  3. STEP/03

    Build

    Built in stages you can see and use, tested with your people before anything goes live.

  4. STEP/04

    Run

    We operate, maintain and extend what we build, or hand it to your team with everything they need to run it.

SEC/D6 · Team

How we keep the numbers right

Validation before writing.
Every extracted field is checked against rules and against the destination system before anything is written.
Confidence and exceptions.
Low-confidence reads go to a person with the source document attached, and the corrections feed the rules.
Collection from websites.
Public data only. Terms of service and robots directives respected. A review before any collection project starts.
Reconciliation.
Counts and totals checked between source and destination on every run.
Traceability.
Every record can be traced back to the document or source it came from.
Handoff.
A runbook covering each source, each mapping and what to do when a source changes its format.

SEC/D7 · Terms

Scope, access, ownership and data handling: see Security and data handling.

SEC/D9 · Next step

Book a Systems Map call

You keep the map.