Skip to main content
Beta
Use case · Deal sourcing

Turn a live acquisition mandate into a target set the deal team can defend

When a mandate starts, weak target reasons create wasted outreach and a longlist nobody can review. Deal leaders, analysts and control owners can keep the bounds, evidence, people, routes, gaps, comments and hand-off state on one mandate record.

Compare Investment Search

Buyer-owned acquisition mandate · Local sample

DS–27 · Workflow-software add-on target review

File owner · Maya Chen

01Decision
Which organisation targets should advance to the corporate-development team’s next review, remain in team review, stay on hold or leave this mandate?
02Target unit
One company organisation record. An asset, property, project, programme, licence, brand or business unit needs its own buyer-owned record and fields.
03Exact Graph One fields
Organisation type is Company · country is the United Kingdom, Germany or the Netherlands · founded in or before 2018 · 30 to 500 employees.
04Buyer-owned field
Category: workflow software for specialist teams. The buyer supplies and owns this field; it is not shown as a built-in Search filter.
05Judged questions
Does available text support the product case? Does it name the customer setting? Does it support the operating model? Each answer needs a reason or stays open.
06Source scope
Shown Graph One organisation and role fields, buyer-owned fields and any source the buyer approves for this mandate. Source use and coverage still need review.
07Excluded from the claim
Seller intent, willingness, ownership, valuation, financials, transaction status, exclusivity, mandate fit, permission to approach and formal diligence facts.
08Reviewer, owner and date
Priya Rao · Corporate-development director · Maya Chen owns the file · review 14 August 2026

DS–27 is a local sample mandate. The mandate owner checks company fit, seller intent and transaction status separately.

Exact Search

Fix the market boundary before judging a target

Country, organisation type, founding year and employee count decide entry to the first set. The buyer-owned category does not become a hidden product field.

Gain over current files: the query, reason, source note, person, route, gap, comment, reviewer and owner stay on the same mandate record instead of splitting across a database, spreadsheet, profile, email and deal Board.

Loading DS–27 · Exact organisation boundary

Evaluative Search

Judge the thesis evidence without ranking deal quality

Buyer-set questions expose the evidence and the missing support. A reason stays open to review; it does not become a fit score.

Loading DS–27 · Judged evidence review

Human target review

Return a target-set decision the whole deal team can inspect

The same four firms keep their exact result, judged reason, source date, gap, person, route, reviewer, owner and next state.

The buyer’s mandate stays on every result, review and hand-off. That lets a deal lead trace why a target moved forward without turning a research state into diligence or approval.

Reviewed target set · DS–27

Advance one. Include one. Hold one. Reject one.

Priya Rao records the target-set review on 14 August 2026. These states direct research and hand-off planning; the deal team checks mandate fit, seller intent, approval, diligence and transaction state.

  1. Advance to hand-off planning

    Workshop Cloud

    Inside all shown exact bounds

    Mina Shah · Founder · role relevance under review

    Judged evidence
    Available local sample text supports the product case. The buyer-owned question names specialist teams, but no allowed customer evidence is shown. The operating model remains open.
    Source and checked date
    Local sample Graph One organisation and role fields · checked 14 August 2026
    Open gap
    Precise customer group, operating model and source coverage
    Route and purpose
    Owen Reed route · ask for internal context · route source checked 12 August 2026
    Reviewer and owner
    Priya Rao · Local sample reviewer · Maya Chen · Corporate-development analyst
    Next action
    Agree the field packet and destination before a formal deal record exists.

  2. Include in team review

    Ridgeway Systems

    Inside all shown exact bounds

    Leo Martin · Product lead · role relevance under review

    Judged evidence
    Available local sample text partly supports the product case. Customer setting and operating model still need analyst review.
    Source and checked date
    Local sample Graph One organisation and role fields · checked 14 August 2026
    Open gap
    Customer setting and operating model
    Route and purpose
    Not checked · no route use assigned
    Reviewer and owner
    Priya Rao · Local sample reviewer · Owen Reed · Origination analyst
    Next action
    Review the named gaps before route work or hand-off.

  3. Hold for source check

    Fieldline Labs

    Inside all shown exact bounds

    Imani Cole · Operations lead · role relevance under review

    Judged evidence
    The local sample record does not hold enough allowed text to judge the product case, customer setting or operating model.
    Source and checked date
    Local sample Graph One organisation and role fields · checked 14 August 2026
    Open gap
    Allowed evidence for all three judged questions
    Route and purpose
    Not checked · held before route work
    Reviewer and owner
    Priya Rao · Local sample reviewer · Maya Chen · Corporate-development analyst
    Next action
    Check an approved source or keep the questions open.

  4. Reject from DS–27

    Stonepath Data

    Outside DS–27 · local sample founded year is 2021

    Not reviewed · exact exclusion

    Judged evidence
    No judged review ran because the local sample founded year fails the exact mandate boundary.
    Source and checked date
    Local sample Graph One organisation field · checked 14 August 2026
    Open gap
    None for this mandate; exact exclusion recorded
    Route and purpose
    Not reviewed · exact exclusion
    Reviewer and owner
    Priya Rao · Local sample reviewer · Maya Chen · Corporate-development analyst
    Next action
    Keep the exclusion reason and checked date; do not open deal work.
Editorial view of one local sample across exact Search, evaluative Search, organisation and person records, relationship paths, a Table, saved Views, comments and a Board. Human review states are working choices, not deal facts.

Organisation dossier

Open the target behind the reviewed row

Workshop Cloud keeps its exact facts, judged evidence, source date, person, route purpose, gap, reviewer, owner and state in one target record.

Buyer or approved-source fields can deepen a live dossier. This sample leaves ownership, financials, valuation, seller intent, mandate fit, transaction and formal diligence facts out.

W
Workshop Cloud
Company target under mandate review · Local sample

DS–27 · Advanced target · Reviewed 14 August 2026

Organisation profile · Sample data

Product case
Supported by available local sample description · Human review required
Customer setting
Open · buyer question names specialist teams; no allowed customer evidence is shown
Operating model
Open · no full judgement from the allowed sample record
Current Graph One organisation profile identity and tabs · Local sample target. No ownership, seller-intent, financial, valuation, mandate-fit or transaction fact is shown.Swipe the tab row or use its arrow keys to review each section.

Person and route

Check the person, source, date and route purpose

Only the advanced target reaches route review. Available relationship evidence supports an internal context request, not permission to approach.

Maya Chen owns the route check. Strength does not prove endorsement, seller intent, willingness, confidentiality clearance or permission to disclose.

MS

Mina Shah

Founder · Workshop Cloud · Local sample

Person profile · Sample data

SummaryNotesInteractionsMutual Connections

Whom could you ask?

Check the evidence on both legs before making the ask.

You Via Target
OR
Via

Owen Reed

Me – Via
Strong
Via – Target
Medium
Path context

Direct on both legs · ask for internal context

Available contact context

Meeting metadata · 12 August 2026 · Local sample

NP
Via

Nina Patel

Me – Via
Medium
Via – Target
Weak
Path context

Second-degree path · not assigned for use

Available contact context

Email metadata · 18 May 2026 · Local sample

Shown relationship strength is evidence; Graph One does not choose whom to ask.Swipe the profile tab row to see every section. Compare both routes, then choose whom to ask

Table, Views and comments

Keep the target set and its review trail together

The full mandate stays editable and reviewable before a target enters private team stages. A saved View can isolate source checks without losing the other decisions.

Loading the DS–27 reviewed target Table

Board review state

Move reviewed targets through private team work

Include, hold, reject and advance are human working choices. The Board keeps comments and owners with the target but does not become the formal deal process.

Workshop Cloud advances only to hand-off planning. No deal stage, seller action or approval is claimed.

Loading the DS–27 private review Board

Shown access state

Named owner, team and inherited folder access. No public link. Retention, offboarding and wider controls belong in the scoped review and contract.

DS–27 target review

Board sharing · Sample data

3 access paths

People with access

Maya Chen

Owns this item

Owner

Corporate development

Workspace share

Can edit

DS–27 target review

Shared folder

Can view
Real Graph One public-link control and access-source labels · Local sample data.

Governed hand-off

Pass one reviewed record without claiming a ready integration

A private Graph One Board is the review layer. The buyer names the authoritative system, field map, transfer method and system owner.

Graph One holds

Mandate brief, exact query, judged reasons, source notes, checked dates, firm and person links, route context, gaps, comments, Views, owners and review state.

Buyer or approved source supplies

Category and deal-shape fields, source-use rules, exclusions, qualified reviewers and any formal deal or diligence material.

Buyer deal system owns

The authoritative deal record, formal stage, diligence, approval, financial, legal, compliance and transaction work.

Hand-off record
DS–27 · Workshop Cloud · advance to hand-off planning
Fields that survive
Target identity, mandate, reason, source class, checked date, gaps, reviewer, state and owner
Formal destination
Buyer’s deal, investment or advisory system · to agree
Method and owner
Import, export or API path and system owner · to agree in scope

This page shows no live integration, export, write-back, deal-room, transaction workflow or completed hand-off. The buyer and Graph One agree the destination, method, field map, access and source terms in scope.

Deal-shape and sector routes

Change the target unit before changing the mandate

Deal shapeTarget unitFields that change
Company acquisition or add-onCompanyBuyer-owned category, product case, customer setting and operating-model fields
Asset or property acquisitionAsset, property or portfolioBuyer-owned place, property and operator-role fields; ownership and transaction facts stay formal
Project or concession reviewProject, package or concessionBuyer-owned stage, owner, adviser, operator and technical-review fields
Programme or licence reviewProgramme, platform or licenceApproved scientific, rights, stage and regulatory-review fields
Site or business-unit reviewSite, plant or business unitBuyer-owned capability, process, equipment, site and separation fields

Adapt the asset, property, project, programme, licence, brand, business-unit, financial and transaction checks to the live mandate.

One mandate · One exact meeting output

  1. 1 · Set the target unit and exact bounds
  2. 2 · Name judged questions, sources and exclusions
  3. 3 · Name the reviewer, owner and formal destination

Test one live mandate against targets, evidence and routes

We will test its target unit, exact fields, source scope, judged questions, dossier, people, route purpose, access, review states and hand-off. The meeting returns one mandate-and-field plan, one reviewed target-set format, one source-and-gap checklist and one formal hand-off packet – not a fit verdict, seller signal, diligence approval, integration, transaction or outcome.