Human agency
Foreframe is built to support professional judgement, not replace it. The person doing the work remains responsible for interpretation, decisions, and final outputs.
Loading library
About Foreframe
The evidence layer for project work
Foreframe is a project intelligence workspace for turning complex source material into cited, review-ready outputs.
It is built for the messy material real projects depend on — reports, presentations, PDFs, images, notes, models, comments, decisions, and changing assumptions.
Why Foreframe exists
Complex work is becoming harder to hold in one place
Important work rarely lives in one clean document. It is scattered across files, folders, decks, reports, screenshots, models, messages, spreadsheets, and meeting notes.
Teams are expected to make decisions from this material, but the evidence is often fragmented, visual, duplicated, or contradictory.
AI can help, but only when it is grounded in context and evidence. Without a visible source trail, generated work is difficult to trust, review, or defend.
What Foreframe is building
From source material to review-ready outputs
Foreframe turns project material into structured evidence, then helps create outputs that can be checked: briefing packs, evidence reports, presentations, tables, summaries, contradiction checks, and interactive experiences.
The goal is not simply to chat with files. The goal is to help people produce work that shows where it came from.
01
Upload project material.
02
Find contradictions and gaps.
03
Generate cited reports and briefings.
04
Review the source trail.
05
Create outputs people can inspect.
Principles
Principles for evidence-led work
Evidence over confidence
Confident answers are not enough. Professional work needs claims that can be traced back to source material.
Context over generic intelligence
Generic AI is useful, but project work depends on specific documents, constraints, language, assumptions, history, and decisions.
Outputs, not just answers
Most teams do not only need summaries. They need reports, briefings, presentations, checks, tables, and next steps that can move work forward.
Tools as evidence channels
Project knowledge lives across tools. Foreframe treats files, folders, models, decks, images, and connected sources as evidence channels.
Clear limits
When evidence is missing, unclear, or contradictory, Foreframe should make that visible rather than hide it behind a polished answer.
Where it starts
Starting with complex, visual project material
Foreframe starts with the kinds of material that are hardest for generic tools to handle well: large visual PDFs, reports, presentations, scans, drawing packs, images, and project documentation.
That makes spatial, design-led, and built-environment work a natural first proving ground — but the underlying problem is broader than one industry.
Large visual PDFs
Reports and presentations
Scans and drawing packs
Images and project documentation
ArchitecturePlanningDesign technologyUrban researchReal estateInfrastructureProduct strategyConsulting
Where it is going
Toward connected project contexts
Foreframe begins with uploaded files and generated artifacts. The longer-term direction is to connect the places where project evidence already lives — documents, presentations, folders, models, design tools, and shared workspaces — and turn them into source snapshots that can support cited work.
This includes ongoing exploration of connected sources such as model snapshots, shared folders, and tool-connected project contexts.
Model snapshots from professional tools
Project folders and shared drives
GIS layers and other professional sources
Tool-connected project contexts
Bring one real project
See what Foreframe can frame — and what it honestly cannot.
Foreframe is being built around real project material — the messy files, evidence, and decisions that shape actual work.