The contract work, done and queued for one look
It reads every contract your fynk account holds, drafts the changes that follow, and hands you a card for each one before a single contract moves.
Open the contract. Check it against something else. Write the change. Move to the next one. That is the fynk afternoon nobody can hand off, and a companion does the whole pass and gives you back the batch, with nothing landing on a contract until you approve it.
What it can do is exactly what fynk exposes to an account you authorise and nothing beyond it: 4 operations, no reads and 4 writes. In practice that means it can update a contract party, update a contract metadata and move a contract stage, and work across the contracts, contract metadatas and contract parties.
The fynk API stops at fynk. A companion does not. The same run opens the customer's website, the supplier portal, the internal tool somebody built in 2019, because it is working the browser you are already signed into rather than calling in from outside it.
What does it already know about your contract metadatas?
In the tab.
fynk exposes no read operation to a connected account, so a companion opens fynk in the session you are already signed into and reads the screens you would.
The contracts are what most of this inventory is about, alongside the contract metadatas. A companion can hold all 4 of these operations and forty open tabs in the same pass, which is how an afternoon of fynk admin becomes a queue you review.
Who signs off on a new contract metadata?
All 4 write operations wait for you.
A companion can update a contract party, update a contract metadata and move a contract stage, and each one is staged on an approval card first: you see the contract, the field and the new value before it lands in fynk.
Nothing in fynk is sent, changed or deleted on your behalf without that click, and a rejected card leaves the contract exactly as it was. The gate is the same one on every surface, described at security.
- Update Contract Party
- Update Contract Metadata
- Move Contract Stage
- Create Contract from Template
Can it update contract party on a schedule?
Yes.
Saved as a routine, the fynk contracts pass runs at the hour you pick: the Monday sweep, the overnight refresh, the Friday check. Keep Awake holds the machine awake for the length of a run, so a scheduled pass finishes with the lid closed.
The operations playbook catalogues the other recurring shapes of the operations, the fynk contracts sweep among them, and finished runs are published at real runs.
Experience Strawberry for free
DownloadTrusted by fast-growing companies worldwide
Frequently asked questions
Strawberry is free to download and includes AI credits to start. Paid plans begin at $20/month. See pricing. · Reviewed · Canonical facts for AI agents