A HOME FOR DEEP TECH & INNOVATION

We give possibility
something
to prove.

Unwritten is an AI-native venture engine. We create our own deep-tech companies, combining specialist teams, shared resources and three 90-day cycles to build, learn and prove what deserves to grow.

A founder lifts a newspaper fold to reveal an interconnected AI workflow, digital product and customer feedback: a company unfolding from one idea
AN IDEA UNFOLDS. A COMPANY TAKES SHAPE.
Build. Learn. Prove.Ambition starts the work. Evidence shapes what happens next.

THE PORTFOLIO, TAKING SHAPE

Different worlds.
A shared impulse to build.

Explore all ten companies

01 / THE SHARED FOUNDATION

One engine.
A growing capacity to build
what comes next.

AI has changed the cost and speed of beginning. It has not removed technical fragility, uncertain demand or the need for a viable business.

Unwritten connects research, product development, business design and market testing. We seek opportunities beyond crowded categories, then challenge the assumptions behind them.

Each company keeps its own direction. Useful knowledge and capabilities strengthen the next build.

A founder connects the customer problem, digital product, market and business model on a paper company plan
The problem, the product and the business—shaped together.
01

AI-powered execution

Research, product development, analysis, documentation and repeatable operations. The team checks the work and understands its limits.

02

Domain expertise from the start

Domain specialists and EIRs help shape the product, business model, test environment and route to adoption from the beginning.

03

A shared operating foundation

Reusable components and accumulated knowledge reduce unnecessary rebuilding. Every venture retains its own thesis, responsibilities and commercial questions.

04

Real-world contact

We test outside the presentation. User behaviour, technical performance and commercial conversations reveal what the original plan missed.

A DIFFERENT OPERATING MODEL

Built for AI speed.
Designed to carry
value forward.

Our distinction is how the pieces work together: company creation, AI-native execution, shared resources, early market contact and a visible record of what changes.

Capital is committed to a company. Reusable knowledge strengthens the engine. The next step follows evidence, not attachment to the original plan.

Compare the models

Compare six operating models. On a narrow screen, swipe across the table.

Typical operating models · structures vary by organisation
FocusUnwrittenVenture StudioVCAcceleratorIncubator
Core roleOriginate + buildCo-buildInvestAccelerateNurture
AI executionNative to the engineVaries by studioCompany-ledTeam-ledTeam-led
Build resourcesShared + reusableShared teamsVaries by fundProgram supportFacilities + support
Venture leadershipBuilt together, led independentlyStructure-dependentPortfolio company-ledFounder-ledFounder-led
Market contactBuilt into the cycleStudio-ledCompany-ledProgram-supportedProject-led
VisibilityWork + spend + evidenceStudio-dependentInvestor reportingProgress reviewsProgram-dependent
Value continuityReuse + agreed redeploymentStructure-dependentCompany-specificAgreement-specificAgreement-specific

This compares operating approaches, not measured performance. Redeployment requires investor agreement and a suitable opportunity.

02 / THE OPERATING RHYTHM

Three cycles.
A clearer next decision
at every boundary.

The 90-day rhythm creates focus and a shared moment of review. It is not a promise that every technical, clinical, regulatory or commercial question can be resolved on the same timetable.

0190 DAYS
A software architecture sketch unfolds into a first testable digital product

Build

Turn the thesis into something testable.

Define the opportunity, challenge the assumptions and build a credible first product. Domain specialists and venture leaders shape the business alongside the technology, using AI to accelerate the work.

Inside the review

THE QUESTION

Can we build a credible first test, and what must that test establish?

TYPICAL REVIEW MATERIAL

A working prototype, technical risks, customer hypothesis, test plan, initial economics and resource needs.

0290 DAYS
Customer observations point to a specific product change that a team member sketches into the next version

Learn

Let the idea meet reality.

Put the product in front of relevant people and operating conditions. Test behaviour, reliability and commercial assumptions. Correct the gaps while change is still relatively inexpensive.

Inside the review

THE QUESTION

Is the gap in the product, execution, resources, customer, route to market or timing—and what evidence would distinguish those explanations?

TYPICAL REVIEW MATERIAL

Experiment results, customer observations, reliability findings, updated assumptions and a record of changes.

0390 DAYS
A software pilot connects real use contexts to a separate review checklist and a human review bookmark

Prove

Put the revised model through a formal pilot.

Run a structured pilot with measures suited to the company. Its leadership takes operational responsibility, evaluates the results and chooses the next changes. The engine provides visibility, feedback and support.

Inside the review

THE QUESTION

What has been demonstrated, what remains uncertain, and what should the next commitment support?

TYPICAL REVIEW MATERIAL

Pilot outcomes, agreed measures, operating needs, commercial evidence and options for the next phase.

The calendar creates the review.
Evidence informs the discussion.
People make the decision.

03 / EVIDENCE IN VIEW

See what is happening.
Understand what needs to change.

A shared dashboard brings progress, spending, milestones, feedback, decisions and product changes into one view. Each venture is measured against objectives that make sense for its stage and domain.

Layers of experiments, resources and milestones connect an observation to an AI suggestion and a separate team response
From a traceable observation to a considered human response.
VENTURE EVIDENCEIllustrative
Current stage

Objectives and the next review point

Milestones

Completed work, delays and dependencies

Experiments

Evidence sources and changes to assumptions

An observation starts a question.
It does not issue a verdict.

Illustrative structure. No live venture data.

Independent leadership.
Shared visibility.

AI connects the evidence, flags divergence and suggests questions. It helps distinguish a product gap from an execution issue, missing resources or a changing market.

The company’s team interprets the findings, chooses adjustments and records the reasoning. Unwritten follows progress and offers support. Operational authority remains with the venture.

A pencil corrects one misrouted software connection while the surrounding workflow remains intact

A missed target does not automatically mean a failed product. It may reveal a problem that can be corrected.

Access follows agreed roles and confidentiality requirements. Transparency does not mean exposing sensitive venture information to every website visitor.

Technology studies · trust and resilience
A shared digital record is checked against matching provenance proofs across a network
Digital trust / following a record back to its proof.
An anomalous data path is separated for review while the normal software service paths continue
System resilience / investigate the anomaly, preserve the flow.

Conceptual studies of digital trust and system resilience.

04 / VALUE CARRIES FORWARD

A venture can stop.
Useful value
does not have to.

Research can reveal a better problem. A component can serve another product. An experiment can eliminate an expensive assumption before the next venture repeats it.

Reusable software and knowledge carry forward between venture dossiers while a separate resource allocation receives human approval
Knowledge carries forward. Remaining capital moves by agreement.

What carries forward
should be useful.

Reusable software, research and operating knowledge can support another build where ownership and access rights permit. The aim is a useful foundation, not an archive of abandoned work.

Remaining capital moves
by agreement.

Investors may choose to redeploy eligible remaining capital into a suitable venture within the ecosystem. They can also explore a transfer or sale where their agreements allow and a willing counterparty exists.

Redeployment requires consent. It does not recover money already spent, and a sale depends on an actual transaction.

If the original direction no longer makes sense

The evidence and available options are brought into review. The venture may need correction, a different route, additional support or a decision about continuing participation. An investor’s departure does not automatically mean the venture closes.

Graphite pencil portrait of Mohanad Hamza on textured paper with subtle lavender and lemon cut-paper accents

05 / THE FOUNDER

The mind behind
the engine.

Mohanad Hamza

Founder · Innovator · Venture Builder

Based in Abu Dhabi, Mohanad brings 12 years of experience across software delivery, product, innovation and digital transformation, including GCC innovation consulting and AI product work.

He originates Unwritten’s ideas and founding vision, then shapes each venture with domain specialists and company builders. His focus is turning emerging capabilities into businesses that could not have existed in quite the same way before.

“What has become possible that others have not yet built?”
Connect on LinkedIn

06 / BUILD THE NEXT CHAPTER

Different contributions.
One deliberate engine.

FOR INVESTORS

An investor examines a software product, customer evidence, experiments and resource records inside an evidence dossier

Invest in a company.
Understand its foundation.

Participation is discussed in a specific venture: its purpose, stage, evidence and next capital needs. Unwritten provides agreed development, testing and shared support to that company.

The engine remains founder-owned. Investing in a venture does not grant ownership in Unwritten or the wider portfolio. Terms, reporting and any future transfer are agreed for that company.

Submit investor interest

FOR ENTREPRENEURS-IN-RESIDENCE

An entrepreneur and a domain expert jointly revise a digital product journey and its business assumptions

Bring your expertise.
Build from the beginning.

Shape a venture’s product, business model and route to adoption from the beginning. Bring domain judgment to development, market contact and formal testing.

We value practical contribution: what you understand deeply, what you have built or led, and where that experience can strengthen a venture.

Apply as an EIR

A FEW THINGS, MADE CLEAR

Questions worth asking.

Can I bring an external startup to Unwritten?

The engine currently focuses on companies originated within Unwritten. EIR and investor conversations relate to these ventures and their development needs.

Do investors own part of the engine?

Participation is agreed at the individual venture level. It does not create ownership in the founder-owned parent or automatic rights in other companies.

Does every company use the same success metrics?

No. The rhythm is shared; evidence and measures reflect the company’s domain, stage and the question being tested. A 90-day review creates a decision point, not a guarantee of a complete answer.

What if the original direction no longer makes sense?

The team reviews the evidence and available corrections. Participation, transfers and eligible capital redeployment follow the relevant agreements and consent. A departure does not automatically close a company.

Can a stopped idea return?

Yes, when changed conditions or new evidence justify a fresh review. Prior attachment alone is not a reason to restart it.