Nous is an AI agent that takes some of the load of life: making good decisions and acting for people in areas where theyâre not the experts, or arenât paying enough attention. We started with bills, where weâre already saving households thousands, and weâre now expanding into new categories. Think Amazon starting with books.
Itâs working. 20x year-on-year growth makes us one of the fastest-scaling startups in the UK, and an NPS of +70 (higher than Apple) says our users love it. On top of bill optimisation, weâve just launched two more products: insurance, where weâre the first in the UK to get regulatory approval to run the full discovery-and-purchase journey as an agent (not just hand you a link). And subscription management, where we use Open Banking to actively cancel unwanted subscriptions for people, rather than just draw them a pretty graph.
Weâre a certified B Corp, and thatâs how we hold ourselves to the mission rather than just talking about it. Weâve stacked the deck: a founding team with multiple exits, and investors including the founders of Monzo, Wise, Booking.com, lastminute.com, Onfido, Funding Circle, Tide and Habito.
The problems are hard, and thatâs the point. Talk is cheap, and that goes for agents too. To have real impact, an agent has to break out of the sandbox and act in the real world, where there are consequences. That means solving all the thorny, frustrating, genuinely interesting problems the real world throws up.
How we build (worth reading before the role)
Most companies split the thinkers, the doers and the builders. We donât. Something special happens when theyâre the same people: a small team that builds and owns the tools for its own problems understands those problems from the inside. So the rule at Nous is simple. The person who feels the problem should be the one who builds the fix.
This isnât brand new. A sharp generalist could always wire something together with no-code and low-code tools to solve a problem. The catch was the ceiling: those tools were far more limited than real code, so you hit a wall the moment the problem got interesting. Unless you had superhuman levels of stubbornness and a high tolerance for using tools for things they really werenât designed for. Whatâs changed is that ceiling. With AI tooling and a lot of context, youâre now building much closer to real code, and shipping it on the live product. You can change how our WhatsApp agent handles a tricky conversation, dig through Open Banking data to find money we should be saving people, prototype a feature, or automate a process that used to eat someoneâs week.
And youâre not doing this around engineering, youâre doing it alongside engineers. Engineers build the safe surfaces you ship on (the tools, the infrastructure, the context APIs, the guardrails), and theyâre who you pull in when you reach the edge of whatâs safe to touch alone.
None of that works without a particular kind of person: not a software engineer, but someone who builds like one.