Field operations software · Built in the UK
Trysquare starts with no fixed idea of your business. You define the records you track, their fields and what connects to what, in the language your business already uses. Then you build your forms, automations and reports on top, and put your own name on the front.
Crawler crane
plant_hire · 6 fields
None of this ships with Trysquare. A plant hire firm could define it in an afternoon, and change it tomorrow.
Why Trysquare
Four things the platform is designed around.
Your records, in your words
You define every record type, field and relationship, in the terms your business already uses, and change them as the business changes.
Your brand throughout
Your name, colours and logo on the app your team uses and on every report your clients receive.
Built for the field
The same forms on the web and on a phone, filled in with or without signal and synced when there is signal again.
Reports without a cap
Branded PDF reports on every plan, with no cap and no per-export fee.
See it in action
Pick a sector to see how a business there could set up the platform: the records it defines, the forms it fills in against them, and the automations that keep people informed. Every name here is yours to choose.
Illustrative example
ISO 27001 / SOC 2
IT & Cybersecurity
An IT security team auditing laptops, cloud servers and SaaS applications could track serial numbers, assigned employees and data sensitivity ratings as evidence for ISO 27001 and SOC 2.
With fields such as
Annual IT Asset Security Review
Checks disk encryption, antivirus status and access control on each asset.
Branding · Every plan
Your organisation name, your palette, your base theme. We are not looking for a credit in the footer.
Your organisation's name
Set the organisation title and description so the platform reads as an internal tool. For most of your team, it simply is one.
Your existing palette
Primary and secondary colours from your own brand guidelines. Buttons, accents and highlights follow them everywhere.
Light, grey, or dark
A site office at 7am and a finance desk at 7pm want different things. Pick the base your team will actually work in.
Adoption without the training day
When software already looks like the company, people stop treating it as another system they have been told to use.
Rowan Fenn Security
Sample dataReports · Every plan
Your client never logs in. What they receive is the PDF - which is exactly why it should carry your letterhead and nobody else's.
Reports that look like yours
Your logo, your header and footer, and your form's own sections in the order you built them.
Straight from the answers
Complete a form in the field, and the responses drop into the template. No re-keying into Word on Monday morning.
No cap, no per-export fee
Generate as many as you need, on every plan.
Pre-use plant inspection
Crawler crane CC-14 · Site 7
1 › Pre-use checks
2 › Components
Components
| Component | Condition | |
|---|---|---|
| 1 | Hoist rope | 1Good |
| 2 | Hook and safety latch | 2Fair |
| 3 | Track tension | 3Poor |
| 4 | Outrigger pads | 1Good |
Actions
Inspected by
Signed by D. Tulloch · 3 Nov 2026, 07:20
Sample data
What you get
The editor is ours and we are opinionated about it. Everything else belongs to you.
Define the things your business actually tracks - tower cranes, rental properties, ventilators, deal rooms - with the fields and relationships you need. No schema migration, no feature request, no waiting on a roadmap.
Build forms in a purpose-built editor. Publishing locks a version, so an inspection filled in last March still reads exactly as it did in March - even after you have changed the questions four times since.
Your logo, your palette, your base theme. Your team logs in to something that looks like it was built for them, because it was.
A subcontractor sees one site. A regional manager sees a portfolio. A director signs off. Set it once, in language that matches how your business already describes itself.
Getting set up
Set up in an afternoon, not a procurement cycle.
Set up the things you track, in your own words: the record types, their fields and how they relate. Bring existing data in from a spreadsheet rather than retyping it.
Lay out your forms against those records. Nest sections, set what is required, publish a version and pin it to the jobs it applies to.
Logo, palette and base theme. Invite the team. From their side, it is simply the company's system.
FAQs
Trysquare starts with no fixed idea of your business. You define the record types you track, their fields and how they relate, in your own terminology, then build your forms, automations and reports on top of them. The platform and every report it produces carry your branding rather than ours.
Nothing. Publishing a version freezes it. Answers are tied to the questions as they were worded at the time, and an assignment started in March keeps the March version.
Not from anything you send them. Your organisation name, logo, colours and base theme apply throughout, and reports come out on your letterhead. The one place our name appears is your workspace's web address. We are not looking for a credit in the footer.
Nearly everything is yours to change: what you track, how it relates, who can see it, and what it all looks like. The form editor is the one fixed part, because a good editor is hard to build and everyone needs the same one.
Trysquare is not open for sign-up yet. Tell us about your business and we will be in touch about early access.