Transformation OS A product of Implemented.Today

Describe how your business runs. Get the whole system back.

Transformation OS keeps your processes, systems, people, conversations and delivery work in one connected workspace. Tell the assistant how things really run. It asks what it needs to know, then drafts the maps, records and tasks with you.

See how it connects

Sign in with Google or Microsoft.

Fig. 1 Illustration A description, and the records it becomes

You tell the assistant

Sales takes the order in Salesforce. Operations re-keys it into SAP, then Finance chases anything that fails the credit check.

The assistant asks

Who re-keys the orders today, and does every order go through the credit check?

  1. 1 Department Sales
  2. 2 System Salesforce
  3. 3 Step Enter order in ERP
  4. 4 Decision Credit OK?

Drafted into your workspace plan. Nothing is created until you ship it.

01The model

One step in a process. Everything it touches.

Process maps, org charts, system lists and task boards usually live in different tools and drift apart. In Transformation OS they are one set of records, linked to each other. Pick a step and follow the thread.

Fig. 2 Illustration Order to Cash, and what each of its steps touches Choose a step to trace it.

01 Process

Where it sits

A step lives on a map, in the lane of the team that runs it.

Order to Cash

  • Credit OK? Finance lane

02 People

Who runs it

An owner and a role, from the same records as the org chart.

Owners and roles

  • Ellie Chen Account Manager
  • Sam Okafor Sales Coordinator
  • Jonas Bruhn Order Processor
  • Greta Lindqvist Credit Controller
  • Aisha Karim Warehouse Lead
  • Priya Raman Head of Operations
  • Marcus Bell Head of Sales

03 Systems

What it runs in

One catalog of systems, each with an owner of its own.

Systems catalog

  • Salesforce Owned by Marcus Bell
  • SAP S/4HANA Owned by Rob Iversen
  • NetSuite Owned by Tomas Ek
  • Manhattan WMS Owned by Aisha Karim
  • EDI Gateway Owned by Ravi Menon
  • Zendesk Owned by Nadia Osei
  • Power BI Owned by Hugo Marín

04 Work

What is changing

Problems found in the process become tasks, estimated and ranked.

Order Automation

  • ORD-1 Remove manual re-key between Salesforce and ERP In Progress
  • ORD-2 Credit hold releases are not reaching the warehouse Code Review
  • ORD-3 Stock levels drift overnight between ERP and WMS In Progress
  • ORD-4 ASN messages rejected by two trade customers To Do
  • ORD-5 Pricing validation step takes 20 minutes per order To Do
  • ORD-6 Add audit trail to credit decisions Backlog
  • ORD-7 Order intake API retry on EDI timeout Deployed to dev

05 Conversation

What is still open

Questions sit on the task they are about until someone answers.

Open questions

  • Do EDI orders go through the re-key too? Asked by Ana Petrova
  • Can we fall back to EDIFACT D96A for those two? Asked by Ola Nowak
  • Do the 2019 pricing tiers still apply to legacy accounts? Asked by Mateo Rossi
  • Which weekend for the ERP cutover, the 14th or the 21st? Asked by Ana Petrova
  • Can the nightly consolidation run under 40 minutes? Asked by Dana Whitfield

Traced

Names, owners, systems and tasks from the Northwind Foods demo workspace.

02How it starts

No blank workspace. No checklist of fields.

You start with a conversation. The assistant asks what it needs to know and builds a plan you can read before anything exists.

Recorded in the product /onboarding
The onboarding screen of Transformation OS: the assistant greets the user and asks what the company is called, with an empty workspace plan and seven setup stages on the right.
The first screen after sign-in, before any answers. Northwind Foods demo workspace.

  1. Sign in

    Use your Google or Microsoft account. The first sign-in creates your account and opens the assistant.

  2. Say who you are

    Give it your company name or website and it looks the company up, so you confirm what it finds instead of typing it all. Or describe the business in your own words.

  3. Answer what it asks

    It works through your business, pain points, workflows, systems and team. When something is unclear it asks, often as options you can pick. Drop in documents or spreadsheets and it reads those too.

  4. Read the plan

    Everything it drafts collects in a workspace plan beside the chat: process maps, systems, departments, roles and people. Nothing is created until you ship it.

  5. Ship it

    Ship creates the workspace: process maps whose steps link to systems, roles and owners, the organization, starter tasks and a first thread of open questions. Prefer to start empty? Create a blank workspace instead.

  6. Keep going

    The assistant stays docked on every page of the workspace. Connect Claude or ChatGPT and they can work in the same workspace, as you.

03The product, recorded

Real screens. Real workflows.

Each clip is a screen recording of the working application, in a demo workspace for Northwind Foods, a fictional company. Nothing here is a mock-up.

01 Process mapping

Map the process as it actually runs.

Draw swimlanes for the departments involved, add steps and decisions, and put the owner, the role and the system on each step. Nest a map under the process it belongs to, or link a step to the process behind it.

Recorded /process-mapper 0:23

What you can do

  • Swimlanes, steps and decisions
  • Owner, role and system on every step
  • Maps nested under a parent, steps linked to child maps
  • A library of every process in the workspace

In this clip

  1. Order to Cash, mapped across the departments that run it
  2. Connect the new step to the one it feeds
  3. Name who runs it, and in which system
  4. Every step carries its system, owner and role

02 Organization

Know who does what, and who they report to.

People, departments and roles, with supervisors on both people and roles. See the same records as a list, as a reporting tree or as a hierarchy chart, and use them as owners and roles in every process map.

Recorded /people 0:16

What you can do

  • People, departments and organizational roles
  • Reporting lines as a tree and a hierarchy chart
  • The same people own steps, systems and tasks
  • Import from a spreadsheet through the assistant

In this clip

  1. Everyone in the organization, with role and department
  2. The same people as a reporting tree
  3. And as a hierarchy chart, one click away

03 Systems and architecture

Catalog the systems and what you build on them.

Every system the business runs on, with its owner. Components form a tree you drag into shape, each with a type, an importance and an estimate for every delivery phase. Phases show the capacity you agreed and the headroom left.

Recorded /components 0:17

What you can do

  • Systems with owners, linked to process steps
  • A component tree you reshape by dragging
  • Estimates per component and delivery phase
  • Capacity, estimated effort and headroom per phase

In this clip

  1. Every component in the workspace, in one tree
  2. Drop it on a parent. It saves on the drop
  3. The structure holds. It is the workspace, not a view
Screenshot, detail /phases
The Phases grid: Discovery, Build wave 1 and Build wave 2, each with start and end dates, capacity, estimated hours, headroom and component count.
Phases in the same workspace: capacity, estimated effort and the headroom left.

04 Delivery tracking

Run the work across every project.

Kanban and list views for each project and for the whole workspace. Save board layouts, rank work by dragging it, and see estimated release dates. Boards update live when someone else moves a card.

Recorded /project/order-automation 0:16

What you can do

  • Board and list, per project and across projects
  • Saved views, shared or private
  • One priority order for the whole workspace
  • Estimated release dates and live board updates

In this clip

  1. Add work where the work is tracked
  2. Estimate it while the context is fresh
  3. On the board, in front of the whole team

05 Conversations

Keep questions next to the work.

Threads sit beside the tasks and processes they are about. Questions are tracked, so the dashboard shows what is waiting on you and what is waiting on a reply. When a message is really a piece of work, turn it into a task that stays linked to the thread.

Recorded /communications 0:21

What you can do

  • Threads on a task or standing on their own
  • Open questions, and who owes the answer
  • One step from a message to a tracked task
  • Mentions, replies and assignments notify by email too

In this clip

  1. Every thread, and the questions still open
  2. When the answer is work, make it a task
  3. Tracked in the project, linked to the thread

06AI across the product

The assistant stays in the room.

The assistant that set up your workspace stays docked on every page. It reads files and spreadsheets you drop in, and imports departments, roles, systems, components or people after you confirm. Claude and ChatGPT can connect to the same workspace as a custom connector, signed in as you.

What a connected assistant can work with

Tasks
Find, create, update and rank tasks
Delivery planning
Components, phases and estimates
Communications
Threads, open questions, notifications
Process maps
Maps, their steps and the systems they use
Organization
People, departments and roles
Artifacts
Reports and plans published to the workspace

No recording here: the assistant answers with a live model, and we would rather describe it than stage it.

04Use cases

Three moments in a transformation.

  1. 01 Discovery

    How does the work actually happen?

    Map it as it runs, not as the handbook says.

    Talk the processes through with the assistant, then refine the maps with the people who run them. With an owner, a role and a system on every step, the gaps between teams, owners and systems show up on the map.

    • Swimlanes by department
    • Owner, role and system per step
    • Open questions tracked, not lost in chat
    Process mapping, recorded

  2. 02 Delivery

    What are we changing, and when?

    Turn findings into estimated, ranked work.

    Each problem becomes a task in a project, ranked in one order for the whole workspace. Components carry estimates per delivery phase against the capacity you agreed, and boards show where every piece of work stands.

    • Boards and lists across projects
    • Phase estimates and headroom
    • Jira sync where it is set up
    Delivery tracking, recorded

  3. 03 Client work

    What does the client need to know this week?

    Give the client the view, not a weekly deck.

    Invite the client into the workspace. They see the dashboard you see: work in progress, open questions and who owes each answer. When Implemented Today delivers the work, Progress Summary sets its tracked hours against the estimates. A report can be shared as a page, by link.

    • One dashboard for both sides
    • Questions with an owner and a status
    • Reports shared by link, no sign-in needed
    Conversations, recorded

05Connections

Connections, stated precisely.

What each connection does today, and who sets it up. No logo wall.

Connection What it does Who sets it up
Claude and ChatGPT Add the workspace as a custom connector over MCP and sign in with your account. The assistant can then read and update tasks, delivery plans, conversations, process maps, the organization and published reports, acting as you. You
Scripts and agents Personal credentials let a script or a coding agent act as you on the same server, limited to the areas you choose. You, in Settings
Spreadsheets Drop a CSV or Excel file into the assistant to import departments, roles, systems, components or people. It shows what it will create and waits for you to confirm. No one, it is built in
Jira Task changes are pushed to Jira as they happen. Every hour, status, assignee, due date and time tracking come back, and new issues under a linked epic become tasks. Comments stay where they were written. Implemented Today, per deployment
GitHub Pull requests, reviews, checks and deployments appear on the task they belong to, matched by its key. Implemented Today, per deployment
Hubstaff Hours tracked by Implemented Today’s delivery team, set against estimates on Progress Summary. Implemented Today
Google Dataplex A data glossary in the workspace can sync its terms with a Dataplex business glossary. Implemented Today, per deployment

06Start

Describe it once. Keep it connected.

Sign in with Google or Microsoft. The assistant starts with one question: what is your company called?

Already have a workspace? Sign in and you go straight to it.

Sign in to Transformation OS

Use the account you already have. The first time, this creates your account and the assistant helps you set up a workspace.

Invited by a colleague? Sign in with the address they used.