Halfcycle is a small firm. We work with engineering organisations that are about to adopt AI for the first time, and with organisations whose AI investment hasn't shown up in productivity. The principals have built and run engineering organisations at scale; the firm is backed by nuCode Tech Capital. We take on a small number of clients at a time and we work closely with each.
Most engineering organisations are still working out how to use AI well. Some are at the start, deciding where to invest and how to run a first pilot. Some have early AI use in production and want to scale it across more teams without losing the gains to coordination overhead. A third group has already invested, and the productivity and cost numbers haven't moved the way they expected. Different surface patterns, but the underlying job tends to look similar: pick the right interventions, and make sure they show up in the metrics.
Most CTOs we talk to have a working theory of where the problems are. What they don't have is the time, the spare engineering capacity, or the political room to pull a team off shipping for three months and rebuild the loop while the rest of the company keeps running. It's real engineering work. Someone has to instrument what's happening, find the parts that are paying back, redesign the parts that aren't, and then ship the result with the team that's going to maintain it.
That kind of work is awkward to staff internally, and the two obvious external options miss it. Big 4 consultancies stop at the strategy document; changes to the CI pipeline aren't in scope. The dev-shop model sells engineering hours by the month, which is the wrong unit. The bottlenecks here are usually about flow and decisions, not hands. Halfcycle exists because the right shape for this work is operators on a fixed scope, and the existing categories don't deliver that.
Halfcycle is backed by nuCode Tech Capital, a Toronto-based venture studio with a portfolio of operating companies across engineering infrastructure, applied AI, and financial systems. The studio put capital and operating support into Halfcycle from the start, and runs the back-office that lets a small consulting firm operate at a higher level than its headcount would suggest: accounting, legal, hiring, infrastructure, and a network of senior operators we can pull in for specific engagements.
In practice, what this means for clients: signing a pilot with Halfcycle gets you more than the people on the engagement. Behind the firm there's a balance sheet, an operating playbook from a studio that has already shipped portfolio companies, and a roster of advisors with engineering and commercial backgrounds we can call on. The firm is deliberately small, but it isn't operating alone.
A few things about how the firm runs that are worth knowing before a first call.
We work with a small number of clients at a time. Every engagement has a principal embedded with the client for the duration. The people who sell the work also do the work; there isn't a senior pitch followed by a junior delivery team. That constraint caps how big the firm gets, which is the trade-off we picked on purpose. If we tell you we're not available for a few months, that's the actual situation.
The discovery call is a fit check, both directions. If your situation would be better served by hiring in-house, by a different kind of firm, or by waiting six months until something else has settled down, we'll tell you. Taking on the wrong engagement costs more than declining one.
Fees are tied to outcomes the client and the firm agree on at the start. The same instrumentation produces the baseline at the beginning and the final measurement at the end. If we didn't move the metric we said we would, we'll say so.
The next step, if any of this is interesting, is a discovery call. We use it as a mutual fit check and as a chance to sketch what a first engagement might look like.