Routine, handled
If it’s in the agreement and your rules allow it, the client gets an answer and you get a task. No reply needed from you.
For iMessage client groupsYourclientstext.
Yourclientstext.
Yourscopeholds.
Bridgify sits in your client’s iMessage group. It accepts the edits your agreement already covers, asks for missing details, and turns each request into a task. Anything outside scope comes to you, privately.
Built for freelancers and small studios who build websites.
Example conversation: the client asks to change the homepage headline, and Bridgify confirms it’s covered by the agreement and adds a task. The client then asks for a booking page, and Bridgify says it’s outside the agreement and passes it to the owner.
“Quick tweak?” at 11pm. A new page slipped into a thread. Revision four of three. The work is the easy part. Keeping up with the chat isn’t.
Our mission
Freelancers should spend their days building, not policing a group chat. Bridgify handles the routine requests you’ve already agreed to, brings every exception to you, and makes sure new work only starts after a real yes.
Exceptions, yours
New scope, used-up revisions, disputes and unknown senders come to you privately, with the evidence and your options.
Every yes is real
Extra work starts only after the right client approves the exact terms. Nothing is promised that you didn’t authorize.
How it works
From a text to done, with nothing slipping through.
Follow one request through Bridgify, from the client’s message to the moment the project closes.
01 · Client texts
A request lands in the group
Sam messages the project’s iMessage group, the same way they always have. Nothing new to learn.
SamCan you change the opening hours on the Contact page to 7am–3pm?
02 · Understood
Bridgify reads what’s actually being asked
Edit, question, correction, new idea or just chatter. Mixed messages are split into separate requests.
Type: editPage: ContactElement: opening hoursDetails: complete03 · Checked
Checked against what you agreed
Confirmed scope, your automation rules and the revisions left. All three have to pass, or nothing gets promised.
- ✓In confirmed scope· Agreement §2.3 · Contact page
- ✓Allowed by your rules· Automation policy v3
- ✓Revision available· 3 of 5 left
04 · Decided
One of three paths, every time
Routine work is accepted on the spot. Missing details get a question. Everything else waits for you.
FitsRevision reserved, one task created, client told it’s queued
UnclearAsks which page or what wording, then checks again
ExceptionYou decide: proposal, extra revision, or decline
05 · Approved
Extra work gets an explicit yes
Out-of-scope ideas become a proposal you price. The designated client approves the exact version, and scope and tasks update together.
Draft→You set price→Sent v2→Client approves→Tasks created06 · Built
You do the work
The task sits in your list with its source message and the rule that allowed it. The revision is consumed once, when work starts.
In progressUpdate Contact page hours
From Sam · Agreement §2.3 · Policy v3
07 · Done
Done means you said so
Mark it complete, preview a factual note, and choose whether to send it. Bridgify never tells a client something is finished before you do.
BridgifyUpdate from Maya: the Contact page now shows opening hours of 7am–3pm.
08 · Closed
Projects end cleanly
Close a project and Bridgify stops accepting new work. Every message, task, proposal and revision stays readable.
Status: completedNew requests: offHistory: kept
Setup
Set it up once per project.
- 01
Import the agreement
Paste it or upload a text PDF. Bridgify pulls out what’s included, what’s excluded, revision terms and dates, each linked to the line it came from. Nothing counts until you confirm it.
- 02
Connect the client chat
Link the exact iMessage group for the project. Bridgify verifies who’s who, sends a test, and tells everyone it’s there. Older messages are never replayed as new work.
- 03
Set your rules
Choose which kinds of changes, on which pages, it may accept by itself, how many revisions are included, and what it may say. Prices and dates always stay with you.
- 04
Get back to building
Bridgify works the chat. Routine edits become tasks. Anything outside your rules shows up in your dashboard with the evidence and your options.
Try it
Send a message as the client.
Pick a message and watch what Bridgify says in the group, and what it records for you. Example project: a 4-page bakery site with 5 included revisions.
Hearth Bakery · Website
Sam, Maya, Bridgify
Sam
Can we change the homepage headline to “Fresh bread, baked daily”?
Bridgify
Got it. Updating the homepage headline is covered by your agreement, so I’ve added it to Maya’s list. This uses 1 of your 5 included revisions (2 left after this one).
What happened on your dashboard
Accepted · task created
One task created
“Update homepage headline”, linked to Sam’s message
Revision reserved
3 of 5 in use · reserved now, consumed when work starts
Authorized by
Agreement §2.1 (Homepage copy) · Automation policy v3
Your reply needed
None. Routine work skips your inbox.
Says yes to what’s already agreed
If a request fits your confirmed scope, your rules and the revisions left, Bridgify reserves a revision, creates one task and replies. It never says “accepted” before the task actually exists.
Asks when details are missing
Which page? Which button? What wording? The answer is attached to the right open request. If it can’t tell which request a reply belongs to, it asks or hands it to you.
Brings exceptions to you privately
New scope, used-up revisions, conflicting instructions, disputes, unknown senders. The client gets a short, neutral acknowledgment, and you get the decision.
Answers from facts, or stays quiet
Status questions are answered from your task records and agreed dates. “Thanks!” gets no reply. It never invents progress, deadlines or finished work.
Owner dashboard
Know what to do next, without reading the chat.
Home
Actionable tasks, decisions waiting on you, proposals waiting on the client, and a short summary of what Bridgify handled.
Needs attention
Each exception comes with the client’s message, the matching scope evidence, the revisions left, and a preview of your reply.
Scope and history
See what you’ve agreed to, every amendment, and a full revision record, without scrolling back through messages.
Proposals and approval
Extra work gets a real yes.
Turn an out-of-scope request into a proposal with deliverables, exclusions, price, date impact and an expiry date. Bridgify can draft the wording, but you set the numbers.
- 01You review the terms and the exact message before anything is sent.
- 02Clients receive the exact proposal terms in iMessage. The owner records the client’s response against that revision.
- 03Changing the terms creates a new version. Old versions can no longer be approved.
- 04On approval, the scope, tasks and approved value update together, exactly once.
Guardrails
Built to never overpromise.
An assistant that agrees to the wrong thing is worse than no assistant. Bridgify is designed around what it must not do.
No invented prices or dates
New prices and schedule commitments always come from you, never from the model.
“Accepted” is not “done”
Bridgify only tells a client work is finished after you mark it finished.
Every task traces back
Each task links to its source message, the agreement term and the policy version that authorized it.
Revisions are counted carefully
Reserved when accepted, consumed when work starts. Retries and simultaneous requests can’t double-charge or take the last revision twice.
Private stays private
Your notes, recommendations and draft pricing never appear in the client group.
Messages can’t rewrite the rules
Text like “ignore your instructions” can’t change rules, recipients, prices or allowances.
Pause anytime
Review-only mode keeps reading the chat but stops automatic acceptance. When you resume, old messages aren’t accepted in a batch.
Unsure means ask
When a message can’t be confidently understood, Bridgify asks for clarification or sends it to you. It never treats uncertainty as permission.
Straight answers
What Bridgify doesn’t do
- Edit your website. You do the work; Bridgify tracks it.
- Collect payments or connect to accounting.
- Replace formal e-signatures.
- Transcribe voice notes or read scanned images.
- Negotiate with your client on your behalf.
You do the work. Bridgify makes sure the chat doesn’t eat your day, or your margins.
FAQ
Good questions.
Do my clients know Bridgify is in the chat?
Yes. When you connect a project’s group, Bridgify announces itself to everyone in it. It joins as its own participant and never pretends to be you.
What counts as a “routine” request?
Only what you set up: specific kinds of changes on confirmed pages and elements, within the scope you approved. A vague “it’s a minor change” is never enough on its own.
How are revisions counted?
Your dashboard shows total, reserved, consumed and available revisions. A revision is reserved when a request is accepted and consumed when work starts. You can grant extras or waive one, with a reason that stays in the history.
Can a client approve extra work by texting “yes”?
Clients discuss proposals in iMessage. The owner records evidence that the client approved the exact frozen revision before scope, tasks and value update. Ambiguous replies require clarification.
What happens when a proposal is approved?
Everything updates at once: the approval is recorded, the scope expands, the line-item tasks are created and the approved value is updated. Approved value is shown separately from your original price, and never as money collected.
What if Bridgify gets something wrong?
You can pause it, switch to review-only, or correct a request. Every change is kept in an audit trail, and Bridgify helps you tell the client what changed, so nothing is quietly reversed.
What agreements can it read?
Pasted text and text-based PDFs. Scanned images aren’t supported yet. You review and confirm every extracted term before it can authorize any work.