Telegraph Systems Solutions logoTelegraph

Process

What working together looks like.

Every engagement starts the same way — understanding how your team works today before anything gets changed. From there it takes one of four shapes.

01 — System audit02 — Focused project03 — Implementation support04 — Ongoing maintenance

Engagement type

01

System audit

A full look at the software you're running and the workflows around it — then a prioritized list of fixes, built and documented.

  1. 01

    Review the software you're running

    I start with what you already own — how each system is configured, what it's being used for, and where two tools are doing the same job.

  2. 02

    Sit with the managers and administrators

    I meet the people who actually do the work and walk their workflows step by step, the way they run them today.

  3. 03

    Build the pain-point list together

    First their list — everything that's frustrating, slow or manual. Then mine, from what I find during the audit that nobody had flagged.

  4. 04

    Suggest solutions, including AI

    Solutions built on the software you already have, plus any practical AI opportunities where they genuinely fit the workflow.

  5. 05

    Build in a sandbox, you approve for live

    Approved changes get built in a test environment first. Your team tests them, signs off, and only then does anything move to live.

  6. 06

    Record the SOP video

    Every change I make gets a short SOP video — for training new hires and for the people who have to live with the new process.

Engagement type

02

Focused project

One pain point or issue that spans multiple parts of the organization — for example a full rebuild of month-end reporting.

  1. 01

    Define the problem, not the symptom

    A focused project is usually one issue that touches several departments, or a whole function that needs rebuilding rather than patching.

  2. 02

    Meet everyone the process touches

    For a month-end reporting rebuild that means the controller, the managers who rely on the reports, and the people who build them.

  3. 03

    Map how it runs today

    What goes in, what comes out, who touches it and where it falls apart in the middle.

  4. 04

    Propose the solution, then build it

    I present the approach before anything gets built, then do the configuration and build work myself.

  5. 05

    Document and hand over

    SOP videos and documentation so the new process survives turnover and doesn't depend on me.

Engagement type

03

Implementation support

You're moving to new software. I become the internal point of contact alongside the controller — so implementing a new system isn't a second full-time job for them.

  1. 01

    Discovery call

    What you're running today, what you're moving to, and where the implementation currently stands.

  2. 02

    I don't replace the vendor's team

    The software vendor still runs their implementation. I sit on your side of the table as the point of contact, doing the work the controller would otherwise be doing after hours.

  3. 03

    Understand the business before configuring

    I review your current system and how your company actually operates first, so I can tell you what to carry over into the new setup and what to leave behind.

  4. 04

    Set it up properly, not generically

    A vendor sets up the baseline. I configure the new system around your cost structure, approvals and job types so you're not fixing the setup a year later.

  5. 05

    Data transfer and a clean go-live

    I help move the data across and pressure-test it so go-live day is uneventful.

  6. 06

    Train before go-live, on your own data

    SOP videos recorded in the sandbox using your data, so the team learns the new system before it goes live — not during.

Engagement type

04

Ongoing maintenance

After an audit, project or implementation, most clients keep me on call for anything system- or process-related.

  1. 01

    On call

    Once we've worked together I know your systems. Clients use me as on-call help for anything related to them.

  2. 02

    Process issues, not vendor bugs

    I don't replace the vendor help desk for software programming problems. If it's a process or configuration issue, I can help.

  3. 03

    A place to troubleshoot ideas

    New pain point, new idea, or something that just isn't working — bring it to me and we'll work out whether it's worth changing.

How it's billed

All of this work — audits, projects, implementations and on-call help — is billed in 15-minute increments. Invoicing is detailed: you see exactly what was worked on, per project or ticket.

See fees & billing

Not sure which one you need?

Most companies aren't. A short call is usually enough to tell whether it's an audit, one focused project, or just a few hours of help.

Book a discovery call Send an intake form