Software products and consultancy

We ship our own products. We help you get yours right

Entyre is a small, senior software company. We build and run Handrail and Regulars, and advise companies on architecture, technology strategy and technical leadership.

Products

We build our own products, and we run them.

Two very different products, one way of working. Designed, built, released and operated by the same team.

B2B SaaSEarly access

Handrail

The back office for small companies.

Meetings, proposals, subscriptions and billing, commission, support and product guides. One customer record walks through all of them, so nothing is re-keyed and nothing falls between tools.

  • Proposals
  • Billing
  • Invoices
  • Helpdesk
  • Knowledge base
  • Meetings
Visit Handrail
Mobile and watch app

Regulars

The golf app for your regular group.

Side games and betting formats settled for you, live scoring for the whole group, and satellite course maps. On the phone in your pocket and the watch on your wrist.

  • iPhone
  • Android
  • Apple Watch
  • Wear OS
  • Live scoring
  • Course maps

Coming soon

Consultancy

Advice from people who still ship.

Architecture, technology strategy, technical leadership and due diligence, from a company that runs its own software in production.

See how an engagement works

Most technical advice comes from people who stopped building years ago, or from people who would like to sell you the build. We are neither.

Entyre builds and runs its own products: a back office platform for companies, and a golf app on phones and watches. We make the architecture decisions, and then we live with them. The release. The support queue. The hosting bill. The migration nobody planned for.

That is the view we bring to your company. We know where a decision ends up once it is in production, because ours end up there too.

We don't do engineering for hire. We won't sell you a team, so we have nothing to gain from recommending a bigger build. You get a straight answer, in writing, from senior people.

What we do
  • Software architecture
  • Fractional CTO and technical leadership
  • Technology strategy
  • Technical due diligence
What we don't
  • Build your product for you
  • Rent out developers
  • Resell tools, clouds or vendors

When to call us

Nobody wakes up wanting an architecture review.

People call when one of these is happening. If you recognise your own company in one of them, that is a good moment to talk.

01 · No one technical at the table
We have a product and customers. We have nobody who can judge the technology.

An agency or a small team built it, and it works. But you can't check what they tell you. You are not sure who holds the code and the accounts. And the big technical calls keep landing on your desk.

02 · Outgrown the first architecture
Every feature takes longer than the last one. Now the team wants a rewrite.

The first architecture got you here. It may not get you further. You need to know if a rewrite is the right call or an expensive detour, and what to do first either way.

03 · A deal on the table
We are about to invest. Can this technology and this team carry the plan?

You are funding a software company, buying one, or preparing your own round. Someone independent has to say what is really there, what is missing and what it will cost to fix.

04 · A decision that is hard to undo
We have to choose, and nobody here has made this choice before.

Build or buy. Which platform. Where AI earns its place and where it doesn't. What to do about a cloud bill that grows faster than revenue. One decision, and it will be expensive to reverse.

How an engagement works

Four formats. Each one ends in writing.

Each one has a clear scope and ends with a document you keep. You can start with the smallest one.

  1. 01

    Second opinion

    One decision, examined properly. We read what exists, talk to the people involved and tell you what we would do in your place, and why.
    What you get
    • A short written recommendation
    • The trade-offs in plain language
    • A call to go through it together
    Ask for a second opinion
  2. 02

    Architecture review

    What is sound, what is risky, what comes first. We read the code, the infrastructure and the way you release. We talk to the team. Then we tell you where the system will hold and where it will not.
    What you get
    • A written report, findings ranked by risk
    • A clear answer on rewrite or repair, if that is the question
    • A plan in order of priority
    • A session with your team to go through it
    Ask about a review
  3. 03

    Technical due diligence

    An independent view before the deal. For investors, boards and buyers, and for founders who want to find the problems before an investor does. Product, architecture, team and risk.
    What you get
    • A written report made for the people deciding, not only for engineers
    • Risks ranked, with a rough cost to fix
    • A session with the board or the investment team
    Ask about due diligence
  4. 04

    Fractional CTO

    Technical leadership without the full-time hire. We join your leadership team, set the technical direction and hold the team and the vendors to it. When you are ready for a permanent CTO, we help you hire one.
    What you get
    • A technology roadmap tied to the business plan
    • Decisions written down as they are made
    • Someone on your side of the table with vendors
    • Help hiring, including our own replacement
    Ask about a fractional CTO

In writing

Every engagement ends in a document. It is yours, and it still makes sense after we have left.

Ranked

You don't get a long list of findings. You get what matters first, what can wait and what to leave alone.

Independent

We have no build to sell you and no vendor to push. If the answer is "change nothing", we say so.

How we work

We look at the whole line.

Running our own products taught us where software goes wrong: in the gaps between the business, the architecture, the team and production. So that is where we look, from the first question to a decision your team can carry out.

  1. 01

    Understand

    We start with the business: what you are trying to do, by when, and what is in the way. Then we read the code, the systems and the numbers.

  2. 02

    Assess

    Architecture, team, delivery and running costs, together. The trouble usually sits between them, not inside one.

  3. 03

    Decide

    A clear recommendation in writing, ranked: what to do first, what can wait, and what to leave alone.

  4. 04

    Follow through

    Advice only counts if it lands. We stay alongside your team while the decisions are carried out, reviewing and adjusting, for as long as you need us.

and back: we check what each decision did, and adjust the next one

Small and senior

You work directly with senior people who have built and run products themselves. No account managers in between.

Whole, not half

We look at the whole system and the business around it, not one piece in isolation.

Proven on our own products

We advise from practice. What we recommend to you is what we use ourselves.

Contact

Bring us the hard decision.

Tell us what you are deciding or what is stuck. We will reply with a straight answer on whether we can help, and which format fits.

Contact

Start a conversation

Tell us what you are deciding or what is stuck. A person reads every message, and one of us replies personally.

What is it about

What is happening, and what you would like to decide.