HINTERLAND

HINTERLAND · Context, connected

The work behind the work.

Your messages, meetings, documents and decisions are connected. Your workflow should be too.

Explore HinterlandSign in to your workspace
  • Private by default
  • No model calls
  • Review before use

Project context

Sample data

Harbour proposal

In progress

  1. Stated intention

    Message · draft

    “Ask for a decision on the timeline without sounding defensive.”

  2. Project objective

    Harbour · objective

    Confirm the phase-two scope before the pilot review.

  3. Prior decision

    [1] Meeting notes · 12 Oct

    Phase two begins only after the pilot review is complete.

  4. Meeting brief

    Preparation · 6 items

    Three questions for Thursday, each tied to a source.

  5. Message draft

    Refinement · draft

    A shorter ask, with the timeline rationale kept intact.

Context stays with the project.

5 items · 3 sources

The problem

The gap

Good work gets lost between conversations.

The information usually exists. What disappears is the thread between it: the reason behind a request, the concern under a note, the commitment made in a meeting.

“The information exists. The continuity doesn’t.”

Isolated tools improve individual messages and summaries. They do not preserve the relationship between intention, context, and outcome.

Where the thread breaks

Five common handoffs

  1. 01

    A message explains the delay.

    Inbox · 14 replies

    The reasoning is there, buried under a thread of follow-ups and side conversations.

  2. 02

    A meeting note records a concern.

    Notes app · untitled

    Useful context, saved somewhere no one will think to reopen before the next meeting.

  3. 03

    A document holds the objective.

    Shared drive · v4 final

    The goal exists, separated from the discussion that shaped it and the people it affects.

  4. 04

    A decision is made out loud.

    Conference room · no record

    The room agrees. The project record stays empty, so the decision has no durable source.

  5. 05

    The same question is reopened.

    New thread · starting again

    The work repeats because the thread between the question, the answer, and the decision was never kept.

Repeated work is rarely a discipline problem. It is a continuity problem.

The solution

Everything connected. Nothing important forgotten.

Hinterland keeps a project’s working context in one place. Each step adds to the same thread instead of creating another disconnected artefact.

  • Context continuity
  • Connected professional information
  • Unified intelligence workflow

One project · one context thread

Intent & audience

What you mean, and who needs to understand it.

Project objectives

The outcome the work is meant to serve.

Source documents

Selected material, visible and removable.

The thread

One working context, visible at every step.

Intent, sources, preparation, communication, decisions, and approved records stay inside the project they belong to.

The MVP connects context, preparation, refinement, approved meeting records, and keyword search.

Meeting preparation

Talking points, questions, and gaps.

Decisions & actions

Only what the supplied material supports.

Approved knowledge

A durable record for the next conversation.

Diagram describes the product model. Document intelligence and personalization are planned after the MVP.

The features

Six capabilities that share one working context.

Hinterland is not a set of disconnected assistants. Each function reads from the same project thread and adds something reviewed back to it. Scope is labeled honestly throughout.

01MVP scope

Communication refinement that keeps your intention intact.

Improve a draft for clarity, structure, tone, and persuasion without changing what you meant. The original text and your stated intention stay visible the entire time.

  • Draft and intention capture
  • Intent-preserving refinement
  • Ambiguity findings
  • Audience alternatives
  • Change explanations
  • Grounding checks
See a refinement preview

Refinement · Harbour proposal

Draft

Original

Kept visible

“I wanted to check whether we can still move the phase-two start. I know we discussed the pilot, but I think the timeline might be tight.”

Stated intention

Ask for a decision without sounding defensive.

Refined · for review

Variant 1/2

“Could we confirm whether phase two can start after the pilot review? That would keep the timeline tied to the outcome we agreed on.”

  • Meaning preserved; the request made explicit.
  • “Might be tight” replaced with a concrete decision point.

Evidence · Pilot review notes [1]

Awaiting approval

Preparation · Pilot review

Brief · draft

Pilot review

Thursday · 4:00 pm · 45 minutes

6 items

What the sources establish

  • The pilot ran for six weeks across two teams. [1]
  • Phase two depends on the review outcome. [1][2]
  • The review criteria were discussed, not finalized. [2]

Questions to raise

  • Which metric decides the review outcome?

    Why · the sources name no criterion.

  • Who signs off on phase two?

    Why · no owner appears in the notes.

Gap · No review owner or deadline is stated in the supplied notes. Both are marked “Not specified.”

02MVP scope

Walk into the meeting with something useful to contribute.

Prepare talking points, questions, gaps, and risks from the sources you choose. Each item shows where it came from, and ungrounded suggestions are marked rather than disguised as fact.

  • Meeting record and agenda
  • Talking points
  • Questions with reasons
  • Gaps and risks
  • Contribution sequence
  • Source transparency
03MVP scope

Turn a conversation into a record you can trust.

Convert supplied notes or a transcript into a summary, decisions, action items, and open questions. Owners and deadlines appear only when stated. Everything else is marked as not specified.

  • Discussion points
  • Confirmed decisions only
  • Action items
  • Open questions
  • Item-level review
  • Approval and audit trail

Meeting record · Pilot review

Approved sample

Pilot review

24 October · Summary generated from supplied notes

Approved

Summary

The team reviewed the six-week pilot, confirmed that phase two depends on the review outcome, and left the review owner and deadline unspecified.

Decisions

1
  • Phase two starts only after the pilot review. [1]

Action items

2
  • Prepare the review summary. [2]Owner · Not specified
  • Confirm the phase-two scope. [2]Deadline · Not specified

Open questions

2
  • Which metric decides the outcome? [1]
  • Who signs off on phase two? [1]
Every item keeps a visible link to its source excerpt.
04Later phase

Understand what a project document is missing.

Analyze a selected document for unsupported claims, logical gaps, inconsistencies, unclear reasoning, and missing context. Connect related documents and decisions so the project reads as one argument. This is a secondary improvement, deliberately planned after the MVP.

  • Missing arguments
  • Logical gaps
  • Inconsistency checks
  • Unclear reasoning
  • Unsupported claims
  • Connected decisions
  • Document-to-project links
  • Review suggestions

Not available in the MVP. The preview below shows the intended direction, not a shipped capability.

Concept preview · Not in the MVP

Document analysis · Research proposal

Read-only sample

Section 3 · Methodology

The proposed sample spans two departments and will be compared against last year’s results.

This approach will produce a representative view of the organisation.

The review process follows the same structure used in the pilot.

Finding

The representativeness claim has no supporting citation or method for sampling.

Findings

  • 01 Claim without support
  • 02 Missing counterargument
  • 03 Unclear reference
Findings are suggestions for review. No content is rewritten or saved automatically.
05Later phase

Improve over time without losing your voice.

Hinterland can eventually notice the patterns behind your strongest writing and offer adjustments you control. Personalization is secondary scope; advanced personalization is long-term.

  • Approved style examples
  • Explicit feedback
  • Visible style summary
  • Editable observations
  • Reset at any time
  • Intent always preserved

Sample observation · 3 drafts

You lead with context.

Your clearest refinements open with the reason before the request.

Suggested pattern

Short asks land better.

Requests under 90 words kept the decision point visible for the reader.

Always editable

Your voice stays yours.

Examples guide structure and tone; they never overwrite your intention.

Observations are visible, editable, and resettable by the user.

Planned · later phase

Planned after the MVP. Any learned preferences would remain visible, editable, and resettable by the user.

Knowledge · Harbour proposal

3 approved records
pilot timelineKeyword
Project · HarbourType · Meeting recordApproved only

  • Pilot review — 24 October

    Approved

    “Phase two begins after the pilot review; the timeline remains tied to that outcome.”

    Decision · Project Harbour

  • Phase-two planning — 2 October

    Approved

    “The pilot timeline was set at six weeks, with a review before any phase-two commitment.”

    Decision · Project Harbour

  • Scope review — 18 September

    Approved

    “Open question: which metric decides the pilot outcome and who owns the review?”

    Open question · Project Harbour

Results come from approved records only. Drafts stay separate.
06MVP scope

Keep approved knowledge within reach.

Approved meeting records become searchable by project, type, date, and topic. Drafts remain separate. You can open a record, trace every decision back to its evidence, and export the result when you need it elsewhere.

  • Approved-only storage
  • Project folders
  • Date and topic filters
  • Keyword search
  • Record detail
  • Export records
  • Clear empty states
Try the sample knowledge search

Interface previews use sample project data. Live generation and file storage are not available on this site.

The workflow

From scattered information to meaningful outcomes.

The MVP follows five connected steps. Each one keeps its sources visible and waits for your review before anything is saved.

  1. 01

    Context input

    Create a project, state its objectives, and select the documents, notes, or agenda that should inform the work.

    MVP capability

  2. 02

    Meeting preparation

    Turn selected context into talking points, questions, gaps, and a contribution sequence for the discussion.

    MVP capability

  3. 03

    Communication refinement

    Improve a draft for its audience while preserving the original text, stated intention, and any commitments.

    MVP capability

  4. 04

    Meeting documentation

    Convert supplied notes into a reviewable summary with decisions, action items, and open questions.

    MVP capability

  5. 05

    Knowledge storage

    Approve the record, then find it later by project, date, type, and keyword. Drafts stay out of knowledge.

    MVP capability

Every step is reviewable. Nothing enters knowledge without explicit approval.

See the stages in motionSee the principles

The experience · six stages

Six stages. One thread of context.

On a motion-enabled desktop, scroll through a working desk. Objects gather, clarify and connect as the work moves from scattered information to an organized record. Every object represents supplied material or a reviewable output.

Interactive on large screens · scroll controlled · no autoplay

The six stages · static view

The interactive desk is available on larger screens with motion enabled. Here is the same sequence, with every object and every gap stated in plain text.

  1. 01Stage 1 of 6

    Scattered information

    A message, a notebook, a project document, a calendar and a task sheet. Each holds a piece of the context. None of them knows the others.

    Nothing connects yet.

    Object board

    5 items

    MessageNotebookProject documentCalendarTask sheet

    Reading order follows the work: source, refinement, preparation, record, knowledge, connection.

  2. 02Stage 2 of 6

    Communication

    The message moves forward. Its structure becomes clearer while the original wording, the stated intention and every commitment stay visible.

    Improvement never hides the source.

    Object board

    3 items

    Original keptIntention preservedReview required

    Reading order follows the work: source, refinement, preparation, record, knowledge, connection.

  3. 03Stage 3 of 6

    Meeting preparation

    The agenda and the documents that matter gather together. Talking points, questions and gaps appear as prompts for your judgement, not as answers.

    Gaps stay marked, never invented.

    Object board

    4 items

    Agenda sourceTalking pointsQuestionsGaps marked

    Reading order follows the work: source, refinement, preparation, record, knowledge, connection.

  4. 04Stage 4 of 6

    Meeting intelligence

    Loose notes become a structured record: key points, decisions, open questions and actions. Missing owners and deadlines remain explicit.

    Placed in order. Traced to the notes.

    Object board

    4 items

    DecisionsActionsQuestionsNot specified

    Reading order follows the work: source, refinement, preparation, record, knowledge, connection.

  5. 05Stage 5 of 6

    Project knowledge

    Approved records connect to the documents they came from. One quiet thread carries the reasoning, the evidence and the decisions forward.

    Approved records only.

    Object board

    3 items

    Approved onlySource visibleSearchable later

    Reading order follows the work: source, refinement, preparation, record, knowledge, connection.

  6. 06Stage 6 of 6

    The connected workspace

    Every object settles into place. Context, conversation and decisions remain connected — reviewable, traceable and still yours.

    Assistance supports judgement, never replaces it.

    Object board

    3 items

    ConnectedTraceableHuman approval

    Reading order follows the work: source, refinement, preparation, record, knowledge, connection.

Inside the product

See how the work holds together.

Five sample views of the product surface, from a draft in review to an approved record you can search.

Preview mode

Nothing here connects to an account, a file store, or a live model. Search runs locally over sample records.

N

Harbour proposal

Preview workspace

Sample data

Original draft

Kept visible
“I wanted to check whether we can still move the phase-two start. I know we discussed the pilot, but I think the timeline might be tight.”

Editable for this preview. Nothing is sent or saved.

Refined · draft

Awaiting approval

“Could we confirm whether phase two can start after the pilot review? That would keep the timeline tied to the outcome we agreed on.”

Change · structure

The request moves to the opening sentence; the rationale follows it.

Change · tone

“Might be tight” becomes a concrete decision point instead of a hedge.

Evidence

Preview actions only
Interface previews use sample project data. Approval, saving, and generation are not available on this site.

Refinement: original text and intention stay visible.

Records: owners and deadlines are never invented.

Knowledge: only approved meeting records are searchable.

Our principles

Principles in practice, not features on a list.

The product is judged by whether it helps you think and act clearly, not by how much it generates.

“Hinterland proposes.
You decide.”

Assistance, not authorship. The user remains responsible for every saved or shared outcome.

Personalized improvement is planned after the MVP. The principle above governs how it will be designed.

01

Context continuity

Every task shows which project and sources it uses. Approved context stays available for later work without silently crossing project boundaries.

02

Intent preservation

Refinement improves clarity, structure, tone, and persuasion without changing what you meant. The original text and intention never disappear.

03

Proactive assistance

Gaps, risks, and missing questions are surfaced as findings you can review, not buried inside polished prose that sounds more certain than the source.

04

Personalized improvement

Suggestions explain themselves, remain editable, and can be reset. Your voice is the standard; the system is only a careful reader.

05

Connected workflow

Preparation, refinement, documentation, and knowledge share one visual grammar and one context thread rather than five disconnected tools.

06

Knowledge retention

Approved decisions, action items, and open questions become durable, dated, searchable records instead of disappearing into a meeting.

Evidence over inferenceHuman approvalPrivacy by defaultHow this is enforced

Use cases

Built for the work you are already doing.

Hinterland is designed for people who carry context between messages, meetings, and documents as part of ordinary professional work.

The MVP is a single-owner workspace. One person controls their projects, sources, records, and access. Cross-organization collaboration is not part of the MVP.

01

Primary audience

Students & early-career professionals

Group projects, internships, and first professional roles.

What changes · Clearer messages, prepared contributions, and a record of decisions that does not depend on memory.

02

Primary audience

Startup teams

Fast-moving product and business work where context lives in chat.

What changes · One project thread from preparation to approved decisions, without inventing another documentation ritual.

03

Primary audience

Corporate professionals & managers

Cross-functional meetings, proposals, and reports.

What changes · A credible point of view before the meeting and outcomes that remain traceable afterward.

04

Primary audience

Researchers & academic teams

Papers, proposals, reviews, and lab or program meetings.

What changes · Preserved reasoning, cited prior decisions, and documentation that stays consistent across collaborators.

Later audiences

Part of the long-term vision. Not targeted by the MVP.

Not in the MVP

Enterprises

Organization-wide context, administration, and cross-team permissions.

Consultants & freelancers

Multiple client workspaces with stricter separation and export needs.

Educational institutions

Cohort workflows, institutional policy, and role-based oversight.

Technology & trust

Built to be trusted with the work behind the work.

The architecture is deliberately conventional. Clear layers, one owner per workspace, and checks that happen on the server rather than in the interface.

Application architecture

Frontend to storage

Layer 01

Frontend

Next.js, React, and TypeScript. Server components by default.

Layer 02

Backend

Supabase Auth and a server-only API layer.

Layer 03

AI processing

A provider-agnostic adapter with bounded, reviewable runs.

Layer 04

Database

PostgreSQL with row-level security and owner isolation.

Layer 05

Document storage

A private bucket with short-lived, owner-scoped access.

The public site is a preview. The workspace runs on Supabase Auth, PostgreSQL with row-level security, and a private document bucket. No AI model is connected.

Product commitments

Trust is a product requirement, not a policy page.

These commitments shape what the interface shows, what the server checks, and what the product refuses to infer.

User-controlled access

Documents, records, and projects belong to one owner. Access is explicit, scoped, and revocable.

Consent-based recording

Future scope

Live audio capture is not in the MVP. When it arrives, recording will require clear consent from participants.

Reviewable outputs

Generated content is a draft. Nothing is saved to knowledge or shared until you explicitly approve it.

Traceability

Decisions, owners, and deadlines carry a reference to the exact source excerpt and location.

Uncertainty handling

Missing owners or deadlines are marked “Not specified.” Unsupported claims are flagged, never filled in.

Access controls

Row-level security and owner-scoped file access are enforced in the database and rechecked in server code.

MVP & roadmap

What is in the first release, and what comes later.

The MVP is five connected capabilities plus the trust requirements that make them safe to use. Everything else is explicitly deferred.

Roadmap items are direction, not commitments. No feature is presented as available before it exists.

In the MVP

Core scope
  1. 01

    Context input

    Projects, objectives, PDF and DOCX extraction, pasted notes, source selection, and deletion.

  2. 02

    Meeting preparation

    Talking points, questions, gaps, risks, and a contribution sequence built from selected sources.

  3. 03

    Communication refinement

    Intent-preserving drafts, ambiguity findings, audience alternatives, and evidence-aware review.

  4. 04

    Meeting documentation

    Summaries, confirmed decisions, action items, open questions, and explicit “Not specified” states.

  5. 05

    Knowledge storage

    Approved-only records, project folders, date and topic filters, keyword search, and record detail.

The MVP is complete only when all five capabilities and the trust requirements are functional together. A partial workflow does not count as a release.

After the MVP

Not scheduled
Planned next

Live meeting assistance

In-meeting prompts and structured capture, subject to a separate consent and reliability design.

Planned next

Audio recording & transcription

Consent-based capture, speaker handling, transcription quality, and retention controls.

Long-term

Advanced personalization

Long-term communication patterns, visible style controls, and a complete reset path.

Long-term

Google Drive import

Bring selected documents into a project without weakening owner-scoped storage.

Long-term

Enterprise workflows

Organization administration, shared governance, and cross-team access models.

Secondary improvements, including document intelligence and style examples, follow the MVP. Audio capture, live assistance, Google Drive import, and enterprise workflows require separate product and legal work.

Begin with context

Make every conversation count.

Keep your ideas clear, your projects connected, and your knowledge within reach.

Create your workspace

Email verification · Private by default

Review before saving. Private by default.

The work behind the work.