Ridgepole

How we work

Start with what matters. Build from there.

We reuse existing components and handle the technical work, so you don't have to assemble a separate data team to get started.
Talk about your businessSee what's possible

Three stages

  1. 1

    Choose the first outcome.

    Systems and process audit

  2. 2

    Connect and build.

    One-time build fee

  3. 3

    Maintain and expand.

    Ongoing maintenance fee

  1. 01Systems and process audit

    Choose the first outcome.

    Understand the decision, recurring work or missing capability that matters most, along with the systems and access you need. Agree what a useful first result does and how your team will use it.

  2. 02One-time build fee

    Connect and build.

    Bring the relevant information together, agree how important figures are defined, and deliver the first useful analysis, workflow or tool. We set up AWS for you as part of the build.

  3. 03Ongoing maintenance fee

    Maintain and expand.

    Keep the agreed connections and software working, and add capabilities on the same foundation as priorities change. Ongoing engineering supports the work as systems, definitions and needs change.

A one-time build fee plus an ongoing maintenance fee, with the AWS setup included. We scope both in discovery and give you an all-in year-one estimate. We never quote a number before we look.

Step one · the audit

The audit gives you a map you can act on.

We walk through your real work and replace assumptions with evidence about your company.

  1. 01

    Trace the work

    Walk through a real decision. Find the sources, handoffs, definitions and manual steps behind it.

  2. 02

    Map the system

    Map which systems hold which information, how often it can refresh, and who may see it.

  3. 03

    Prove one route

    Agree a proof and how we accept it: one sample change reaches the agreed view, with its update time shown.

  4. 04

    Sequence the build

    A prioritized build sequence with scope limits, dependencies and open risks.

Source coverage matrix

Illustrative format
Work areaSource categoriesQuestion to resolve
Revenue and marginAccounting + purchasingHow are shared costs assigned?
Capacity and deliveryScheduling + staffingWhich record is current?
Customer responseOrders + knowledgeWhat may each role see?
Revenue cycleBilling + collectionsWhat update schedule is possible?

An example of the deliverable format, not findings about a real company.

Below every good answer

The foundation does more than move files.

Pick a layer to compare the manual version with the connected one.

Manual / Custom connectors

  1. Export
  2. Download
  3. Upload again

Exports go stale as soon as work changes. Someone repeats every download.

Connected / Custom connectors

  1. Source change
  2. Checked input
  3. Refresh record

Connectors are built for your systems from our library, not generic ones. Each source refreshes on its supported schedule, and a failed update is visible.

Reuse

Reusable infrastructure, built for you.

We customize reusable infrastructure to fit your business and turn it into software your company can use. Speed comes from reuse, not shortcuts.

Pieces of reusable infrastructure
120
Typical time for a team to build it from scratch
6 to 12 months
Source systems joined in one live build
6+

Connectors

Custom connectors, not generic ones.

Each company's data has its own shape, so we build connectors and the database to fit your systems, inside your private cloud. Generic connectors read the surface. Ours are shaped to how your systems actually hold the data.

Systems we connect

  • Accounting
  • Payroll
  • Scheduling
  • Billing
  • CRM
  • Purchasing
  • Operations
  • Spreadsheets

We build a connector for each system you use, from our library. If a system has an API or an export, we can connect it.

Where it runs

Your private cloud, set up for you.

Everything runs in a private AWS environment. We set it up for you and give you access, and the cost is part of the build. We collect the minimum we need and control who sees what.

  • Encryption
  • Tenant access controls
  • Sensitive-data audit logging
  • HIPAA technical safeguards

The same discipline lines up with what SOC 2 and SOX auditors look for. We walk you through exactly what is covered during scoping.

Handoff

You are never locked in to us as people.

  • Infrastructure as code
  • Documented migrations
  • Runbooks
  • A handoff plan in the contract

What would you like to understand or get done?

A question your systems can't answer. Work your team repeats. A tool you wish existed. Tell us where you want to start.

Talk about your business