Would HubSpot be required to use Agreedio?

No. Phase 1 and Phase 2 do not require CRM setup. HubSpot is conditional Phase 3 work only.

Would contract text leave by default?

No. The planned default is summary fields and links only. Copying contract files or text would need separate explicit authorisation.

Would a marketplace listing bring customers?

That is not guaranteed. Listing follows a supported integration and approval; it is not proof of demand or distribution.

ConditionalConditional · Phase 3

HubSpot would stay connected to agreement records, not replace them.

This conditional Phase 3 module would show an agreement summary on a HubSpot company record, with clear install, use and revoke flows. No contract text would leave Agreedio by default. A marketplace listing would not be treated as guaranteed traffic.

Try the sample agreement Join the preview

No sales call required

HubSpot · agreement summaryConditionalFictional sample

Alder Works · company record

Active agreements: 1
Next decision: 2 Jul 2027
Owner: Maya Okafor
Source: Agreedio · AGR-0142

Phase 3. A summary card on the company record, with install, use and revoke flows. No contract text leaves the workspace by default.

Interactive preview · fictional sampleA conditional HubSpot company-record summary with status, dates, link and sync controls.

Why this is labelled the way it is

This ships only if retained paying agreement users repeatedly need HubSpot context, at least five share the job, OAuth/source-of-truth checks pass, and economics hold.

01Conditional

A company record would show a summary card.

If this ships, HubSpot would show a link, status, owner, term end and confirmed notice date for an agreement. The Agreedio record would remain the source for signed terms.

HubSpot · agreement summaryConditionalFictional sample

Alder Works · company record

Active agreements: 1
Next decision: 2 Jul 2027
Owner: Maya Okafor
Source: Agreedio · AGR-0142

Phase 3. A summary card on the company record, with install, use and revoke flows. No contract text leaves the workspace by default.

The conditional summary card shows agreement status and dates without contract text.

02Conditional

Install, use and revoke would be explicit.

A workspace admin would install with least necessary scopes, choose pipelines or fields and revoke access when needed. Disconnect would stop future reads and writes.

Document source · one connectorPlannedFictional sample

Contracts / Signed / 2026

read-only

Alder_Works_SOW_S1_signed.pdf
Alder_Works_Amendment_A1.pdf
Fernhill_Order_Form.pdf

Phase 2. One connector, chosen from measured demand: Google Drive or Microsoft 365, not both by default. Files are imported for review; nothing is confirmed automatically.

The connection screen shows scopes, selected fields and revoke state.

03Conditional

CRM data would create candidates, not signed facts.

Deal amount, description and stage would help only as proposal context, but they would not overwrite a confirmed signed term. Mismatches would become review candidates.

AGR-0142 · Design retainer — Alder WorksFictional sample

Design retainer — Alder Works

CustomerStatement of workMaya Okafor

Effective start: 1 Oct 2026
Initial term end: 30 Sep 2027
Monthly fee: USD 6,500
Notice period: 90 calendar days before term end
Notice method and recipient: Written notice to the named contact
Auto-renewal: Not stated

Governing sources

SOW-S1 (signed, 21 Sep 2026)
Amendment A1 (signed, 15 Mar 2027)
Schedule 2 (attachment, not governing)

Amendment A1 § 3

Either party may give notice not to renew at least ninety (90) calendar days before the end of the term.

Confirmed by Maya Okafor on 18 Mar 2027, based on Amendment A1 § 3.

Signed terms stay on the agreement record when CRM values differ.

04Conditional

Marketplace listing would not be the plan.

Marketplace submission requires supported scopes, help, uninstall and approval. A listing might help discovery, but it is not guaranteed distribution or proof of demand.

Get started · Northline StudioFictional sample

One agreement, end to end

3/6

No agent, model, CRM or connector setup is needed to finish this list.

The support checklist must pass before any integration is called supported.

How it works

How this would work, if it ships.

Conditional on retained customers needing it. The steps below describe the intended behaviour, not an available feature.

01
Connect an authorised portal
An admin would approve exact scopes and bind the portal to the workspace.
02
Choose fields and direction
Selected company, deal, contact, status and date fields would be previewed before use.
03
Review sync candidates and conflicts
CRM changes would not overwrite confirmed signed terms; conflicts would be queued for review.
04
Revoke, disconnect or reconcile
Revocation would stop future work, and reconciliation would make failures visible.

What it does not do.

It is conditional Phase 3 work and is not required for onboarding or first value.
It would not replace HubSpot, become a CRM or manage sales pipelines.
It would not send contract text or files to HubSpot by default.
It would not promise support for every HubSpot edition, object or marketplace approval.
It would not let a CRM edit overwrite confirmed signed agreement terms.
It would not treat a marketplace listing as guaranteed traffic or customer demand.

Related.

Common questions.

Start with one agreement.

Open the fictional sample and walk it from import to a renewal decision. When the paid beta opens, upload one agreement you are authorised to share.