Skip to content
Ziplabs

Enterprise AI · Venture building

Enterprise AI, from opportunity to working systems.

Ziplabs explores where AI can change how enterprises work. It builds the product and the system around it, then develops the strongest opportunities into new businesses.

A working AI system, drawn as a circuit boardConceptual illustration. A model sits at the centre as one component. Around it, inside the harness, are tools connected through MCP, memory, context, orchestration, guardrails, evaluations, identity and observability. Technical connectors link it to enterprise systems, data and the workflow. The board plugs into a gold edge labelled customer need, adoption, people, unit economics and go-to-market: the business it has to fit.C1C2C3C4HARNESSU4TOOLS · MCPtool useU2CONTEXTretrievalU5ORCHESTRATIONagent loopU8IDENTITYleast privilegeU9EVALSoutcome checksU6OBSERVABILITYtraces · costU1MODELselectedper taskJ1 ENTERPRISE SYSTEMSJ2 DATACUSTOMER NEED · ADOPTION · PEOPLEUNIT ECONOMICS · GO-TO-MARKET
Fig. 01 · The model is one componentConceptual

What we do

Enterprise AI often stalls between a promising demonstration and a system people depend on. We work across that whole distance.

The gaps are rarely only technical. A product has to fit how people work, the system has to hold up in daily use and the economics have to justify the change. We work on all three together, from customer discovery through product development to the business case.

  1. 01

    Exploration

    Customer discovery around an expensive problem, and a reason AI now changes what is possible.

  2. 02

    Product strategy

    Who the product serves, what it replaces and why an enterprise would adopt it.

  3. 03

    System design

    Where the path stays fixed, where an agent decides and what it may touch.

  4. 04

    Product development

    Building the software, with the evaluations, tracing and recovery that hold up in daily use.

  5. 05

    Market validation

    Evidence from users and buyers that the product is worth adopting and paying for.

  6. 06

    Commercialization

    Go-to-market, pricing, partnerships and the team the business requires.

How we develop an opportunity

Perspective

What decides whether enterprise AI works.

The model matters. So does the software built around it and the business it has to serve. These views shape what we pursue and how we build.

  • 01

    Start with the work.

    The opportunity is work that is expensive today and people willing to change how they do it. The answer may be a new AI-native product, an end-to-end workflow redesign or a narrower change in one part of the work. The choice of model, and how much autonomy it gets, follows from that.

    Related terms: Workflow redesign · Adoption

  • 02

    Give the model only the choices the task needs.

    Where the path is known, a fixed workflow is usually easier to predict and test. An agent loop is worth its cost when the next step depends on what the last one found. The architecture makes that choice. Orchestration coordinates what runs, which tools are called and where the work passes to a person. A second agent is justified only when it adds something substantive, such as work that can run in parallel.

    Related terms: Agentic workflows · Orchestration · Multi-agent

  • 03

    Much of the reliability lives in the harness.

    The software around the model keeps task state, selects what each call sees and carries out tool calls. Context is chosen for relevance and stale material is cleared as the task runs. Decision memory that outlives a task, including what was decided and why, needs rules of its own.

    Related terms: Agent harness · Context engineering · Decision memory

  • 04

    Integration raises questions of authority.

    MCP connects agents to tools and data, while A2A supports communication between agents. Access scopes can limit what a connection may reach. The business still defines decision rights, including what an agent may do on someone’s behalf, when a person must intervene and who remains accountable for the outcome.

    Related terms: MCP · A2A · Decision rights

  • 05

    Evaluate what a run leaves behind.

    Evaluations run tasks that resemble the real work and check the resulting records rather than the agent’s report of success. Those results guide the next change to the software. Traces show failures, latency and cost. Idempotent operations keep a retry from sending a payment or a message twice.

    Related terms: Evaluations · Observability · Reliability

  • 06

    Price what the customer uses.

    Token prices are the visible cost. Outcome-based economics start from what it costs to deliver a result the customer accepts, with discarded attempts counted and the customer’s review effort measured beside it. The choice of model shifts both, along with how quickly a result arrives.

    Related terms: Unit economics · Model selection · Latency

  • 07

    Value shows up in the workflow.

    AI usage can grow while the business stays the same. Value realization depends on the workflow changing around what the system does well, people adopting it at scale and outcomes that justify what it costs to run. Over time those changes become part of an AI-enabled operating model, which a competitor cannot copy by adopting the same model.

    Related terms: Operating models · Scaled adoption · Defensibility

Current work

Examples of the work.

Selected explorations in organizational context, agent actions and evidence-driven decisions, alongside a broader interest in AI-native business applications and agentic workflows.

Organizational context

An agent working across a company needs the relationships, decisions and history that explain the record in front of it, and a way to see where each part came from.

Direction

Exploring how agents can draw on an organization’s records, relationships and decision history across systems, with provenance, currency, permission boundaries and unknowns made explicit.

Read more about organizational context

Agent actions and accountability

As agents begin to act across enterprise systems, organizations need to grant useful autonomy and still know what was done, on whose authority and with what result.

Direction

Autonomy granted in proportion to what a task requires and what an agent has shown it can do reliably, with the authority behind each action clear and its effects open to review.

Read more about agent actions and accountability

Investigations and evidence synthesis

When complex questions span enterprise systems, relevant evidence rarely arrives in one place. The challenge is connecting those pieces into a coherent account of what happened, what remains uncertain and what deserves attention next.

Direction

Exploring agent-assisted investigations that connect evidence across systems, surface gaps and support faster, better-grounded human decisions.

Read more about investigations and evidence synthesis

Leadership

Sajjad Masud

Enterprise AI Operating Executive and Product Leader

His background spans hands-on engineering in AI and machine learning, distributed systems and databases through product and operating leadership as CPO and CEO. At Ziplabs, he brings product strategy, technical architecture and commercialization together to develop enterprise AI software and businesses.

About Ziplabs

Contact

Start a conversation.

We welcome conversations with enterprise leaders, founders, investors and potential partners working on problems where AI could change how the work gets done.