NxSync · Founder — Product Strategy
One umbrella, several enterprise operating problems
System 04 in the atlas · Enterprise software & AI
NxSync began with a frustration from my own businesses: the systems available to run them never quite fitted how decisions were actually made. Most enterprise software is a decades-old architecture with a chatbot attached — software you adapt your business to, rather than the reverse.
It is an umbrella, not a single product. Marketing operations, enterprise resource planning and secure information exchange are different problems, each getting its own product: NxSync MaaS, NxSync ERP and NxSync SecureShare, held together by one operating discipline rather than one shared codebase.
Why one umbrella over different problems
Every NxSync product starts as a written business problem, not a feature list. Before development begins, the problem, the intended user and what a working solution must demonstrably do are set down, and each piece of work is cut into bounded stages that can be reviewed against that intent.
That discipline (define finished before you start, check the result against the definition, keep a human accountable at each approval gate) is the same one I learned commissioning buildings. NxSync is what it looks like applied to enterprise software: a shared method, not a shared feature set.
What sits under the umbrella
NxSync MaaS treats marketing as a coordination problem (keeping brand, content, campaigns and attribution connected) rather than a content-generation problem. NxSync ERP treats enterprise operations as a schema problem: build the frontend around contracts the backend exposes, so it does not need rebuilding each time the ERP grows. NxSync SecureShare handles the narrower, already-solved problem of controlled information exchange between parties who cannot use ordinary file sharing.
VeraKeep and GrowthOS sit alongside these in a different relationship. Both are independent, open-source systems — VeraKeep for AI-assisted project continuity, GrowthOS for evidence-led growth diagnosis. If either is ever offered as enterprise SaaS, that commercial edition sits within the NxSync portfolio; the open-source project itself is not owned by NxSync.

My role
I define the business problem, the product direction, the requirements and the acceptance criteria for each NxSync product, and I make the release decisions. The building happens through development contributors and AI-assisted workflows in bounded, reviewable stages, with every stage checked against the written intent before it ships.
Current stage
NxSync ERP is under active development ahead of commercial launch. NxSync SecureShare is in operational use as a virtual data room. NxSync MaaS is a designed and architected product programme, not yet deployed commercially. VeraKeep is in working use, open source; GrowthOS is open source and read-only R&D — neither has an enterprise SaaS edition available today.
Explore the portfolio
What the work taught me
The value of enterprise-product leadership is not the number of tools installed; it is the ability to evaluate a business problem, select or build the right system, and stay involved until the outcome works. Translating business requirements into structured, reviewable development work is a discipline that transfers across marketing, operations and information governance alike.
Building software this way surfaced a problem of its own: reasoning disappearing between AI sessions, which is what VeraKeep was built to address.