How it works
Spire stays the source of truth.
Tinsmith fits over the top.
No second customer list, no copied inventory, no other system of record. Everything financial stays in Spire. Tinsmith handles the field work and writes it back.
Architecture
How the pieces fit together.
A single integration layer sits between your Spire company and the Tinsmith app. Every read and every write in the product goes through it.
Your side
Tinsmith
How data moves
Two directions. Zero re-keying.
Live
Straight from Spire
Stock, prices, customers and orders are read from Spire when someone opens a screen, not from a copy. An order created in Spire shows up on the dispatch board on its next refresh.
Instant
Back to the same order
Assignments, parts, quotes, notes, photos, signatures and job status are written to the Spire sales order as they happen, each with a one-time key so a retry can never double-post.
Queued
Sent when the connection returns
Work done without a connection waits on the phone in order and sends itself when signal comes back. The tech can see what’s still waiting.
| What | Lives in | Visible in Spire desktop |
|---|---|---|
| Customers, ship-to addresses | Spire | ✓ |
| Inventory, warehouses (including trucks), pricing | Spire | ✓ |
| Quotes and sales orders, lines, parts used | Spire | ✓ |
| Who’s assigned, when, and the job’s status | Spire order fields + Tinsmith | ✓ |
| Notes, signatures, photos | Spire notes + Tinsmith files | ✓ |
| Time on job by phase, truck counts, availability, multi-day visits | Tinsmith | Summarised on the order |
Connecting to Spire
Two ways to connect. Neither touches your Spire server.
Tinsmith runs in the cloud wherever Spire lives. The only difference is how it reaches Spire.
Spire Cloud
Connected in an afternoon
We need your Spire Cloud address and a dedicated API user. No network work on your side.
- Encrypted connection to your Spire Cloud endpoint
- No VPN, no port forwarding
- A Tinsmith-only Spire user, so every change is traceable
Spire on your own server
A private, encrypted tunnel
A small connector runs on a separate machine in your office and opens a private encrypted link to your Tinsmith instance. Nothing is installed on the Spire server.
- Nothing on your network opened to the internet
- Spire server performance untouched
- We handle the cloud side; we walk your IT through the office side
Onboarding
From signing up to fully rolled out, in about four weeks.
Setup includes a Gemini Logic engineer working alongside your team for the whole month. Most teams are doing real work in Tinsmith by the end of week two.
Week 1
Connect and configure
We connect to Spire, check your customer and inventory data, and set up your job types, techs, skills, trucks and working hours.
Week 2
Office training
A session with dispatch and the office: the board, crews, notes and files, and where Tinsmith’s work shows up in Spire.
Week 3
Field rollout
A few techs install it on their phones and run live jobs while we tune it to how you work.
Week 4
Everyone live
The whole team is on Tinsmith for real work. We check in daily until everyone is comfortable, and we stay on the phone after.
Security
Built like it holds your customers’ data.
Your own instance
A dedicated server, database, sign-in and file storage for each company. Nothing shared with other customers.
Encrypted end to end
TLS 1.3 in transit. Database, backups and files encrypted at rest.
Backed up daily
30 days of database backups, versioned files, and regular test restores.
See it working on your own Spire data.
Book a 30-minute walkthrough with the team that built it. We’ll show you a real dispatch board and a real tech’s day, with no slides and no pressure.