TenthNode›How We Work
The Process

Two entry points.
One direction.

Both paths lead to the same place: operations that run themselves. Fixed scope, fixed fee, everything yours on delivery.

Automation Deployment

From kick-off to go-live in 3 weeks.

This is the timeline for a standard single-workflow build. More complex engagements covering multiple workflows are scoped and sequenced clearly upfront.

Week 1
Scoping and design
Kick-off call to map the current workflow end to end
System access and credentials collected
Edge cases and exception logic defined
Integration points confirmed across all connected platforms
Workflow design signed off: you approve before build starts
Week 2
Build and integration
Automation built in a staging environment against your live systems
All integrations connected and tested with real data
Exception handling and alerting configured
Your team not involved. No disruption to operations.
Week 3
Testing and go-live
User acceptance testing: typically two to three hours of your team's time
Edge cases validated against real transaction samples
Monitoring and alerting confirmed
Go-live with you watching the first runs
Documentation and handover package delivered
How Every Engagement Works

What you can expect from us.

Fixed scope, agreed in writing

Before any build starts, you have a written scope document that describes exactly what will be built, what systems will be integrated and what the workflow will do. Nothing is built outside that scope without your agreement.

No internal tech function required

Your involvement during the build is minimal. You need to provide access credentials and be available to answer questions about your process. That is it. We handle architecture, build, integration and testing.

You are not locked in

All infrastructure accounts are in your name. All workflow documentation is yours. All credentials are handed over. The system keeps running whether or not you continue working with TenthNode.

Exceptions are designed in, not patched on

The workflow is built to handle your most common scenarios automatically and surface anything it cannot handle for human review. We design the exception logic before build, not after something goes wrong.

Technology Strategy and Implementation

For when the problem is bigger than one workflow.

No internal tech function. New asset. Not sure which platforms to buy or where to start. This is a different engagement: broader scope, longer timeline, same senior-led approach.

01

You tell us where you are headed

New asset. Growing portfolio. No tech function. Not sure which platforms to buy. We start by understanding the operation as it is and where it needs to get to. No assumptions, no pre-packaged answers.

02

We map the full picture

Stack assessment, vendor evaluation, integration requirements, automation opportunities, sequencing. Before anything is bought or configured, you have a clear view of what the architecture should look like and why.

03

We do the work

Vendor negotiation, implementation direction, integration builds, automation layer. Randall leads everything directly. No account managers, no junior handoffs. Senior practitioner throughout.

04

You run independently when the engagement ends

Every vendor relationship, every workflow, every document is yours. Most clients are running independently within 12 to 18 months. That is the goal from day one.

Most clients are running independently within 12 to 18 months. Senior practitioner throughout. No handoffs, no layers.
FAQ

Common questions about the process.

For a standard single-workflow build, the internal time requirement is about four to six hours total across three weeks. This includes an initial scoping call, answering questions during build and a user acceptance testing session before go-live. The build itself does not disrupt your operations.
If something material changes (a system turns out to have different API behaviour than expected or you identify an additional edge case during testing), we discuss it directly. Minor adjustments are absorbed. Significant scope changes are scoped and agreed separately before work continues.
Yes. You own the workflow, the documentation and the infrastructure accounts. Most clients are comfortable running it independently after handover. If you prefer TenthNode to continue running it, we offer that as a managed service.
A written description of what the workflow does and how it is structured, credentials and access instructions for all integrated systems, guidance on monitoring and what to do if something flags for review, and contact information for the platforms involved.
The automation build is a focused, time-boxed delivery: one workflow, three weeks, fixed fee. The Technology Strategy engagement is broader and longer, typically 12 to 18 months, covering platform selection, vendor management, architecture and multiple builds across your full stack. Both are led by Randall directly.
Ready to start?

Tell us which workflow is
costing you the most time.

We scope it in days. You have a proposal before the end of the week.

Talk to Us