Know what you are carrying
before you raise,
hire or scale.

An independent review of what has actually been built. Two days or one week, fixed fee, written by someone who has run a software business through two acquisitions and still writes code.

From the river Isla in Angus.
Inver-: the mouth of a river. The point where one thing meets another.

Software gets built faster than it used to. A working product proves that it runs, not that it will hold. And at some point the technology decisions matter more than the technology team can carry alone: a raise coming, an acquirer asking questions, a platform that needs rebuilding, an AI roadmap nobody can test.

The people offering a view are usually selling something, or have never shipped any of it themselves.

Inverisla exists to close that gap. Nothing is sold on the back of the review, so the findings are about the software rather than about what you should buy next.

Founders who need an honest read before a raise, a hire or a rebuild. Boards and investors who want an independent view of a platform before they commit, or after a founder has told them everything is fine. Leadership teams who have been given an AI roadmap by a vendor and have no way to tell how much of it is real.

Mostly hospitality technology, because that is where thirty years of pattern recognition is deepest. The pattern travels.

It usually starts with one of these.

  • "Nobody is sure who actually owns the code."
  • "Every time we fix something, something else breaks."
  • "We are raising next year and nobody has looked at the platform in three years."
  • "One developer knows how it all fits together, and we cannot afford to find out what happens if they leave."
  • "Our vendor has an AI roadmap. We have no way to tell if any of it is real."
  • "We are about to spend a lot on a rebuild and we are not sure it is the right call."

If one of those sounds familiar, the review is the place to start.

How the review works

Two sizes, one piece of work.

Two days. Initial assessment.

A short, independent look at the areas carrying the most risk. It ends with a findings memo: what stands out, what needs attention first, and a clear view on whether a fuller review is justified.

It stands on its own. A board can act on the memo without commissioning anything further.

One week. Full review.

A hands-on review of what has actually been built, assessed against where the business is trying to get to. Most reviews run a week. Where there is more than one codebase or product, or the ownership questions need real digging, it is two, and you will know that from the scoping call along with the fee.

  • Architecture, and what it will carry. How the system is put together, whether it holds as usage grows, and which decisions will be expensive to reverse later.
  • Code quality where it matters. Not style. Whether the abstractions are coherent, whether the tests cover the things that would actually break, and whether someone new could work in it without a guided tour.
  • Security and data handling. Authentication, access control, secrets management, and whether customer data is properly isolated. This is where fast-built products fail most often and most publicly.
  • Ownership and key person risk. Who owns the IP, what the contracts say, and how much of the system lives in one person's head.
  • Infrastructure and cost. What it runs on, what it costs now, and what the curve looks like at ten times the load.
  • Delivery. Whether the team can ship a change safely. Environments, deployment, rollback, and what happens when something breaks at the wrong moment.
  • AI, on the same terms as everything else. What has been built with it, what the vendors are really delivering, and what the roadmap can actually carry. Assessed as engineering, not as a category of its own.
  • Diligence readiness. What a technical due diligence process would surface, and what is worth fixing before it does.

A written report and a prioritised list that separates what needs fixing before you go further from what can wait. Where it helps, that includes how to describe the outstanding items to an investor or an acquirer, because the answer is almost never that there is nothing outstanding.

The output is what to do next, not what to buy next.

Most reviews end with a recommendation and a handover. Some end with a request to stay on. When that happens it takes one of three shapes, each scoped and priced separately.

Fractional leadership. Senior technical and commercial leadership without the hire, for the months it takes to act on the findings. Platform decisions, vendor strategy, an AI roadmap, or preparation for a raise or a sale. Scope set up front, reviewed on a fixed cadence, sized to what the business needs rather than a retainer that bills whether or not it earns.

Advisory and board. Monthly bandwidth and pattern recognition for founders. Governance and a second opinion on the technology for boards and investors.

Implementation. Technical work that turns a decision into something running in the business. Integration architecture, automation of real operating tasks, agent workflows, proofs of concept that move ideas out of slideware. The technical work is mine, not subcontracted.

If you already know which of these you need, skip the review and book the call.

Built on operating experience, not theory.

Inverisla is led by Colin Winning. Thirty years in software and technology, the last fifteen in hospitality, including thirteen years at ResDiary as CTO and then CEO, where the business doubled in size and went through acquisitions by Reef in 2022 and Access Group in 2023.

At Access Group, Colin held commercial accountability for the combined reservations portfolio, and most recently led platform integration work: moving Access Hospitality's products onto the Group platform, unifying third-party integrations into a common framework, and building a developer portal and app marketplace for third-party developers.

The technical side is current rather than retrospective. He still writes, builds and deploys code with the current generation of AI tooling, and still ships things that run rather than demo. That is what makes the review useful. Judging whether someone else's architecture holds up is difficult if you stopped building a decade ago.

Previously
ResDiary Reef Access Group

Writing
on the shift.

A weekly series on LinkedIn. It follows AI, consolidation and pricing through one industry in detail, because that is where the pattern is easiest to see. Very little of it is specific to that industry.

The guest still chooses. The operator still doesn't.

Google added agentic food ordering to Maps with Square and Toast. A Brooklyn pizzeria now shows six ways to order on one screen, two costing card processing and the rest costing commission. Preferred by this business is a label, not a rule, and nothing on that screen tells the guest which route costs the restaurant what.

Read on LinkedIn

A working product no longer proves anyone understood how it was built.

A social network for AI agents shipped without its founder writing a line of code. Researchers found the database key in the site's own JavaScript with row level security switched off, giving read and write access to production. The write access is the more interesting half, because nobody can now say which posts on that platform were real.

Read on LinkedIn

The operator gets the data. The dependency gets deeper.

SevenRooms opened hundreds of millions of DoorDash and Deliveroo customer records to partner restaurants, so a venue can recognise a first-time guest at check-in. In May the argument was that the operator gets the booking and the platform gets the guest. This inverts it, and the thing you gain access to is only yours while you stay on that stack.

Read on LinkedIn
Contact

Start with a call.

Most reviews begin with a 30-minute call to talk through where you are, what is prompting the question, and whether this is the right fit. No agenda required.

Book a call

Or use the form. Replies within two working days.

Thanks - message received. I'll reply within two working days. If your enquiry is time-sensitive and you'd rather speak directly, you can also book a 30-minute call using the button above.
Sorry - something went wrong. Please try again in a moment. If the problem persists, find me on LinkedIn instead.

We handle your data per the privacy notice