Lineage & Lessons Learned

p6k is the third generation in a lineage of enterprise platforms. Each one informed the next. This is not a reboot — it is a culmination.

Generation 1: Glide (ServiceNow)

What It Was

Glide was the codename for the ServiceNow platform in its early days — a cloud-native workflow engine built to modernize IT service management. It replaced clunky, on-premise ITSM tools and went on to become one of the most successful enterprise platforms of the last twenty years.

What Worked

• Platform thinking — ServiceNow wasn’t just an app, it was a platform others could build on
• Workflow as the core primitive — everything was a workflow, which made the system incredibly flexible
• Cloud-native from the start — at a time when competitors were on-premise, this was a massive advantage
• Land with IT, expand everywhere — IT was the wedge, but the platform could serve any department

What We Learned

• Starting with IT created a gravity well — the platform’s DNA is ITSM, and every expansion carries that baggage
• Enterprise sales cycles are long and expensive; the platform was powerful but not accessible to smaller organizations
• Configuration was powerful but complex — you needed specialists (ServiceNow admins/developers) to get real value
• The platform was built before AI; retrofitting intelligence onto a traditional workflow engine has limits

Generation 2: F8 (Dreamtsoft)

What It Was

F8 was a next-generation platform built from scratch at Dreamtsoft. It took the lessons from ServiceNow and reimagined the architecture — highly componentized, modular, and designed for flexibility.

What Worked

• Component-based architecture — everything was a composable building block
• Modularity — the platform could be assembled differently for different use cases
• Expanding beyond IT — F8 started moving into MSP, Sales, and Marketing workflows
• Modern tech stack — built with contemporary tools and patterns

What We Learned

• Modularity is powerful but needs strong opinions about defaults — too much flexibility without guidance overwhelms users
• Expanding beyond IT is the right direction, but doing it incrementally (IT → MSP → Sales) is slow
• The platform needed to be smarter about helping users get started — configuration is not the same as guidance
• The market was ready for something that didn’t just provide tools but actually told you what to do with them

Generation 3: p6k (Playbook)

Beyond aPaaS

Both Glide and F8 were aPaaS platforms — Application Platform as a Service. They were generic platforms you could build SaaS products on. And both discovered, through years of use, that most business applications are built on the same foundational abstractions: organizations, people, things, work, events, transactions. ServiceNow called them Configuration Items, Incidents, Users; Salesforce called them Accounts, Contacts, Opportunities. The universal objects were always there, buried under domain-specific names.

p6k makes this explicit. It ships with eight root objects — universal base tables that every application is built on: Organizations, People, Locations, Things, Work, Events, Transactions, and Relationships. These are not IT-flavored or sales-flavored. They are industry-agnostic from the start. See root-objects.

And because AI is native to the platform, the root objects become the universal grammar that the AI uses to understand any business. When p6k interviews a business owner, it maps what it hears onto root objects and specializes from there. The AI never starts from a blank page. This is what separates p6k from an aPaaS with AI bolted on: AI and the universal data ontology are designed together.

The Synthesis

p6k takes the best of both generations and adds what neither had:

What’s Different This Time

1. AI in the foundations — not adding AI to an existing platform, but building the platform around it
2. Universal root objects — the foundational abstractions that Glide and Salesforce discovered implicitly, p6k ships explicitly — industry-agnostic, AI-readable, and carrying platform capabilities from day one
3. Audience-first — not starting with a niche (IT) and expanding; starting broad and going deep
4. Opinionated defaults with flexibility — OOB playbooks get you running; customization lets you make it yours
5. Accessible — enterprise-grade doesn’t have to mean enterprise-complexity

Built on Itself

At ServiceNow we built the platform first (Glide), then built ITSM on top of it, using the platform — same tables, same workflows, same UI primitives a customer would use. That was the credibility proof: our flagship product is just an app on the platform we’re selling you, so anything we build, you can build.

p6k carries that forward and adds a layer:

• Plagentic apps are apps on the platform. The core system app and every vertical (ITSM, CRM, HR, …) are built from the same primitives the platform exposes — root objects, components, workflows, jelly, the CRUD pipeline. What we ship, you can ship.
• The platform evolves itself through its own loop. p6k-in-p6k: the engine’s own SPECs, Plans, and Generate stages run through the Business Evolution loop we sell (Conversation → Knowledge → Plan → Spec → Generate → Publish). We author p6k the way a customer authors a playbook; s_plan owns the review status of our changesets exactly as it will theirs.

ServiceNow proved the platform by building an app on it. p6k proves the platform by building and evolving the platform itself on it — the loop we sell is the loop we run. There is no privileged, hidden “real” way to build p6k; the AI authoring path is the path. That self-referential closure is hard to fake and compounds over time.

Why This Lineage Matters

Most enterprise software is built by people who have never run the kind of business they’re selling to. p6k is built by people who have built enterprise platforms twice before — and learned, each time, what the next generation had to fix.

Glide taught us that platforms beat apps, and that workflows are the right primitive. F8 taught us that modularity without opinionated defaults overwhelms users, and that incrementally expanding out of IT is too slow. Both taught us — through years of building on them — that every business application is built on the same universal abstractions, even when those abstractions wear domain-specific names. p6k starts where those lessons end: universal root objects from day one, opinionated where it matters, AI at the core, and accessible to businesses that have never been able to afford operational infrastructure before.

This is the third try. It’s the one we’ve been pointing at the whole time.