Founder
He only had a vision, but decided to act on it. Twenty-five years building and running large technology programs, and managing dozens of software teams. He built the entire Genacy platform himself, using AI as the engineering team, and wrote none of the code.
The thread connecting the founder’s story to Genacy.
His father’s knowledge could no longer be asked for.
What would let children understand the world he knew?
25 years in technology, with AI doing the engineering.
Preserve memories and ways of thinking for family.
That was the question. Not a demo, not a prototype — an enterprise-scale application with authentication, a database, permissions, payments, security and thousands of tests, built by one person who would direct every decision and write none of the code.
Everything changed in late November 2025, when Opus 4.5 was released. Before it, the loop was exhausting: the model was confident, frequently wrong, and lost the thread across long pieces of work. After it, a model could hold a whole architecture in its head, follow a written method, and be trusted with a session's worth of work at a time. That release is the reason this project exists.
The answer turned out to be yes, with a large caveat: it works when the human brings the engineering discipline. Decide before building. Validate four ways. Write every lesson down as a rule the next session has to follow. Without that, AI produces very confident code that does the wrong thing, very quickly.
A working platform with twins, guardians, a family wall, voice, historical figures and a death-activation flow — built alongside a full-time job for under A$3,000 in AI usage.
Every session, every failure and every rule that came out of it is written up on this site.
He has written technical and AI strategies end to end — the governance, the policy, the safeguards and the plan to actually implement them — and run one of the earliest enterprise evaluations of an AI assistant, testing fit, security and real business value before anyone rolled it out. Then he proved the method by building Genacy with AI as the engineering team.
A consistent record of taking programs in serious trouble through to release: a city-scale network with less than eight months to go before a global sporting event, an e-commerce platform after three previous managers had failed, a productivity transformation that had been stalled for three years. All shipped.
National platforms used by tens of thousands of operators. A credit-risk engine built by a team of around 300 and signed off by a prudential regulator. Core systems replaced across large, multi-site organisations without interrupting service. Deep infrastructure experience across on-premises, network, cloud and edge.
Understand the business problem first, in the client's language. Design who does what and where decisions sit. Technology last, as the enabler. Build it the other way round and you get a platform that works and a business that cannot use it.
Philip Grech, on solution designI use innovation and I don't blindly follow. Yesterday's technology is not suited to tomorrow.
Philip GrechThe same order of operations produced Genacy: a month of decisions before any code, then structured sessions with AI, with every lesson banked as a rule. The whole story, including the day a tool reported success while writing nothing at all, is in How we build.
Coming soon · First 2,000 trial users only
Help shape Genacy and keep the early-member benefit for life.
Join the beta trial