Stuff we've built

Morph

Knowledge that shows its sources.

Morph reads what arrives about the people and organisations you work with, from email and calendars to documents, news, and the web, and keeps a running record of each one. Ask it for a brief, a profile, or a proposal, and every claim points back to where it came from.

How it works

How Morph works: sources, lake, records, outputsSources such as email, calendars, documents, news, and web search flow into the lake, where material is kept as it arrived. Agents add what they find to records for each client, company, and opportunity, never overwriting each other. Lenses compose outputs such as briefs, profiles, proposals, and capability decks, and every claim's citation points back to the source in the lake.SourcesEmailCalendarsDocumentsNewsWeb searchLakeKEPT AS ITARRIVEDRecordsClientCompanyOpportunityAGENTS ADD,NEVER OVERWRITEOutputsBriefProfileProposalCapability deckEVERY CLAIM CITEDCITATIONS POINT BACK TO THE SOURCE

Material comes in

Connectors bring in email (like Gmail), calendars (like Google Calendar), documents (like Google Drive), news, and web search, as well as data from your own systems. It's kept exactly as it arrived, and nothing ever changes it.

Records build up

Specialist agents work out what each piece is about, and add what they find to the right record: summaries, transcripts, and facts. They add to each other's work; they never overwrite it.

Outputs go out

A lens composes a finished document from the records, citing every claim. Each output keeps the version of the lens that made it, so you can reproduce it exactly, or re-run it fresh.

Facts with receipts

The parts that fetch material never interpret it. Only agents state facts, and only with a citation, so you can check any claim against what it came from.

Morph reads and derives. It never sends, messages, or transacts on anyone's behalf.

Outputs you design

Lenses are written and versioned by whoever runs the install, so the outputs fit your business, not a template we chose. Change a lens, and older outputs stay tied to the version that made them.

What you could build on it

We use Morph for FediCRM. The same engine fits anywhere you need documents assembled from what you know, with the sources to prove it.

A shared CRM

FediCRM runs on Morph: a brief on every client and opportunity, shared only as far as each partner allows.

FediCRM

Questionnaire answering

Compliance and due diligence questionnaires answered from your policies, evidence, and past answers, with every answer citing the document behind it, for a person to check before it goes out.

Pitch decks and CVs

Your people's profiles and past work, matched to a client's needs or an RFP's criteria, so each deck or CV is written for the reader in front of it.

Your data, under your key

Material in the lake, and the records built from it, are encrypted under keys that belong to each account. Erasing an account's content means destroying its key, then removing the material.

We design Morph, and the platform under it, for SOC 2 and GDPR readiness.

Run your own

Morph is software, not a subscription. You can buy the code with a licence to use it, on its own or with FediCRM, and install it in your own environment. Morph has no front end for your users: you bring the product, or we build it with you. Setup, support, and updates aren't included.

Often goes with

Building a product on Morph is a Solutions Architecture question: what your data is, where it comes from, and what you need out of it.

Ready for a conversation?

No sales pitch. No obligation. Just a chat about what you're building and where the opportunities might be.