AlphaCore · Contract lifecycle
Internal betaEvery contract, kept on one record.
Draft from your own templates and clause library, negotiate with the other side, route it for approval and sign it. Then keep the obligations and renewal dates it creates on the same record, with every change on it.
- The other side reviews with an emailed code, no account needed
- Signing order, signed copy and signing record
- Obligations with owners, due dates and recurrence
- 01Drafting
- 02Internal review
- 03Negotiation
- 04Approval
- 05Signature
- 06Active
- 07Renewal
Before AlphaCore
A contract shouldn't live in four places.
01 · Thread
Agreed in an email thread
The terms were settled three replies deep. The wording everyone agreed to is in an attachment someone forwarded.
02 · Folder
Saved as FINAL (2)
Versions pile up in a shared folder. Which one was signed depends on who you ask.
03 · Tracker
Dates in a spreadsheet
Renewal and payment dates live in a tracker that someone updates by hand, until the week nobody does.
04 · Record
One record in AlphaCore
The agreement, its versions, parties, dates, obligations and history sit on one record with its own number. If it was signed somewhere else, register it as an existing contract and keep it the same way.
- A record number your team can quote
- Being drafted → Out for signature → In effect
- Start a new contract or register a signed one
One record, every phase
From the first draft to the day it renews.
01 · Draft
Draft from your clause library
Start from a template and pull in clauses your team has approved. Clauses are versioned and can carry a fallback you've agreed to accept. Write with suggested changes, comments and versions, or bring in a Word file along with its tracked changes.
- Templates with version history
- Standard, fallback and playbook clauses
- Word import and export
02 · Negotiate
Negotiate with the other side
Send a review link. The other side signs in, or confirms a code sent to their email, then comments and proposes wording against a fixed copy. You accept or reject each proposal, so the draft only changes when you say so.
- Comment, redline and download, set per invite
- Links expire after 7 days by default
03 · Approve
Route it for approval
Set approval steps for each record type: who approves, in what order and how long they have. A phase move can wait on approval, so nothing reaches signature before it's signed off.
- Approvers in order or all at once
- Timeouts, with auto-approve only if you allow it
04 · Sign
Sign it, with a record of signing
Prepare a fixed signing copy, place the signature fields, set the signing order and send. Once everyone has signed, download the signed agreement and its signing record.
- Signing order, resend and cancel
- Signed agreement plus signing record
05 · Keep
Keep what it promised
Obligations become work with an owner, a due date and a recurrence: payments, deliveries, compliance checks. Overdue ones are flagged, and each can link back to the clause it came from.
- Payment, delivery, compliance, warranty and more
- Pending → In progress → Fulfilled, or Overdue
Phase rules
Decide how strict the path is.
Each record type follows its own phases. Choose whether they run strictly in order, allow skips and steps back under your rules, or stay open. The record shows which moves are possible now, what's blocking the rest, and which move comes next.
Services agreement · phase order
- Drafting
- Internal review
- Negotiation
- Approval
- Signature
- Active
Phases run in order. No skipping, no stepping back.
Moves from Negotiation
- ApprovalRecommended: negotiation is closedNext
- SignaturePhases run in orderBlocked
- Internal reviewStepping back is offBlocked
Clauses and playbooks
Clauses you can find, and trust.
Keep approved wording in a versioned library, with the fallbacks your team will accept and the playbook positions it won't. Search it by meaning rather than exact words, and check a draft against your playbook before it goes out.
Clause library · search by meaning
- Limitation of liabilityv4StandardMedium risk
- Limitation of liability, mutual capv2FallbackLow risk
- Uncapped indemnityv3PlaybookHigh risk
Draft vs. your playbook
- Limitation of liabilityMatches standard
- Payment termsAcceptable fallback
- Governing lawDeviates
- Data protectionMissing
- Ask a named reviewer to approve a clause or request changes
- Findings come with suggested wording you can apply
- Playbook review uses AlphaCore AI credits
After signing
The promises become someone's work.
Each obligation has an owner, a due date and a recurrence, and links back to the clause it came from. Add them yourself, or accept the ones FyBrain suggests from the contract text.
Services agreement · obligations
1 overdue
Monthly service fee
Payment · Monthly · from §4.2
in 6 daysPendingPriya RamanQuarterly usage report
Reporting · Quarterly · from §6.1
in 3 weeksIn progressDaniel OkaforInsurance certificate
Insurance · Yearly · from §11.3
doneFulfilledMei TanakaSecurity audit
Audit · Once · from §9.4
3 days lateOverdueLucas FerreiraRenewal notice
Renewal · Yearly · from §4.5
Accept to assignin 2 monthsSuggested
Renewals and notice
Renewals you decide on, not discover.
Each contract carries its renewal terms: renew automatically, run a renewal workflow, or let it end. Reminders go out on the schedule you set before the notice window closes, so the decision gets made while there's still time.
Services agreement · renewal
Upcoming- Term
- 12 months
- Notice period
- 60 days
- Renewals so far
- 2 of 5
- Next renewal
- in 4 months
Reminders go to the people you choose, and an escalation can follow if nobody acts. A renewal workflow can require approval above a contract value you set.
FyBrain Ask
Ask the contract, see where it says so.
Ask in plain words and get an answer drawn from the contract and its documents, with every claim linked to its source. What it can suggest (clauses, obligations, dates, risks, tags) waits for you to accept.
What's missing from this draft?
There is no data protection clause, which your playbook requires for vendor agreements.
Playbook: Data protection
The notice period for termination is blank.
§12.2 Termination
History and relations
Every change leaves a mark.
The record keeps its own history: phase moves, approvals, accepted proposals, signatures and fulfilled obligations, whether made by a person or the system. Amendments and change orders link to the contract they change, and proposed changes to key terms wait for approval before they apply.
Created from the Services agreement template
PersonPriya Raman
Proposal accepted: payment within 15 days
PersonPriya Raman
Approved by legal
PersonMei Tanaka
Sent for signature, signing order set
PersonPriya Raman
Signed by both parties. Status: In effect
SystemSigning
Obligation fulfilled: insurance certificate
PersonDaniel Okafor
Obligation overdue: security audit
SystemObligations
Linked contracts
Amendment of
Services agreement
Term 12 → 24 months · pending approval
Change order of
Services agreement
Applied
Related to
Data processing addendum
In effect
A separate audit log records every create, update, share, approval and archive, filterable by person and date.
Plans
Start with one contract, grow by the contract.
Plans are sized by how many contracts you keep active and how much AI work you run. The free plan holds one active contract with its whole lifecycle.
Free
$0/ month
Experience the full system
- Contracts
- 1 active
- AI credits
- 50 a month
- Obligations
- 5 per contract
Solo
$199/ month
Professional contract management
- Contracts
- 2 active
- AI credits
- 200 a month
- Obligations
- 25 per contract
Growth
$299/ month
Full contract operations
- Contracts
- 8 active
- AI credits
- 500 a month
- Obligations
- Unlimited
Scale
$699/ month
Scaling contract portfolios
- Contracts
- 20 active
- AI credits
- 1,500 a month
- Obligations
- Unlimited
Business
$1,499/ month
Enterprise-grade CLM
- Contracts
- 60 active
- AI credits
- 5,000 a month
- Obligations
- Unlimited
Enterprise
Custom
Mission-critical infrastructure
- Contracts
- Unlimited
- AI credits
- By contract
- Obligations
- Unlimited
Annual billing costs less; the pricing page has both.
Questions
What people ask before they start.
What is AlphaCore?
AlphaCore is Fyboard's contract lifecycle module. Each contract is a record that carries its drafts, parties, approvals, signing, obligations, renewal terms and history, from the first draft to renewal or termination.
Is AlphaCore available now?
AlphaCore is in internal beta. Some parts, including workflows and tags, are still switched off in production while they're finished.
Can we bring in contracts we've already signed?
Yes. Register an existing contract to track it: add the signed copy, record its dates and terms, and keep its obligations and renewal on the record from then on.
Does the other side need an account to review a draft?
No. You can invite them with an account or by email, where they get a link and a one-time code. You choose whether they can comment, propose wording or download, and links expire after seven days by default.
Does AlphaCore include e-signature?
Yes. Prepare a fixed signing copy, place the signature fields, set the signing order and send. When signing is complete you can download the signed agreement and its signing record.
How are obligations tracked?
Each obligation has a type, an owner, a due date and a recurrence, and can link back to the clause it came from. Add them yourself or accept the ones FyBrain suggests. Overdue obligations are flagged on the record.
What does the AI do?
FyBrain Ask answers questions about a contract with links to the source text. FyBrain can also suggest clauses, obligations, dates, risks and tags, and playbook review checks a draft against your standard positions and suggests wording. Nothing is applied until you accept it.
How much does AlphaCore cost?
There's a free plan for one active contract. Paid plans are sized by active contracts and AI jobs; the AlphaCore pricing page has the current plans and what each includes.
AlphaCore
Your next contract, on one record.
Start with one agreement. Draft a new one or register one you've already signed, and keep it the same way from there.