Spots scope creep in client messages and turns it into a signed change order.
Fenceline in about a minute. Sound on.
The video and screenshots are design previews of the product we’re building.
About Fenceline
Every studio has a client who asks for “one quick thing”. The request is fair and usually small, so you do it. Twelve quick things later the project is 30% over budget, and nobody ever agreed to that.
Fenceline reads your statement of work once and turns it into a scope map: every deliverable, every revision round, and everything you excluded. Then it watches the places clients ask for things: Gmail threads and Slack Connect channels, with Linear and Asana comments to follow. It only reads threads from that client’s domains, and it never posts anywhere on its own.
When a request falls outside the map, you get a quiet flag with the clause it conflicts with. One click drafts a friendly change order, with an estimate based on your rate and how long similar work took you before. The client approves it from a link, and the line item lands on their next invoice. The relationship stays polite and the margin stays where you priced it.
What founding backers get
The Studio plan for life: 15 active clients, 5 team seats, unlimited change orders, every channel (Gmail, Slack Connect, Linear, Asana) and every invoicing integration (Stripe, QuickBooks, Xero). Future price $49/month.
The pitch
Kfir's answers, in their own words. Day Zero checks the founder's identity, not these claims.
How far along are you?
Pre-launch. The product is in development, and the video and screenshots on this page are design previews of it. The first release covers SOW import (PDF, Google Docs, Notion), the scope map, Gmail and Slack Connect monitoring, change orders with client approval links, and Stripe invoicing. Linear and Asana comments, QuickBooks and Xero, and a shared view for a client’s project manager follow.
Scope creep rarely comes from difficult clients. It comes from small, reasonable asks that nobody wants to make awkward, and together they add up to work that never gets billed. Fenceline catches those asks when they arrive and makes the change order the easy, polite option.
What's new about what you're making?
Scope lives in a PDF nobody re-reads, and requests arrive through four channels. Today studios rely on memory, gut feel, or a project manager who plays bad cop. Fenceline connects the two automatically and cites the exact clause, so the conversation is about the contract, not about whether you’re being difficult.
Who are your competitors?
Project tools like Productive and Teamwork track hours against budget, so they show the overrun after it has happened. A few new tools ask you to paste a client message in by hand. We don’t think anyone will remember to paste it. The check has to sit in the inbox and catch the request when it arrives, before someone types “sure, no problem”.
Are people using your product?
Not yet. Fenceline is pre-launch, so there are no users or paying customers. Founding backers on Day Zero will be the first.
How does it handle the gray zone? "Can you make the logo pop more" is technically inside revision round 2 of 3. I don't want to send a change order for that and look petty.
That's the most common case, and it's why there are three labels instead of two: In scope, Gray area and Out of scope. Revision requests count against your rounds and show as "Round 2 of 3 used", nothing more. You only get a change-order prompt once the rounds run out or the ask is new work. You can also set a goodwill budget per client, say 3 hours a month, and anything under it gets logged quietly.
Only threads with the email domains you attach to each client. Everything else is skipped before it reaches our servers. The Google permission is read-only, and we keep only the snippet that triggered a flag, never the full email. You can see and delete every stored snippet per client.
It starts from your hourly or day rate, then looks at how long similar line items took on past change orders, plus your time tracker if you connect Harvest or Toggl. It always shows a range and the past jobs it used. Nothing reaches the client until you've edited and sent it. In early access people change the suggested number about 40% of the time, usually upward.
If you bill hourly and a client has ever asked for "one small thing", probably. Freelancers in early access recover about 6 billable hours a month on average. If you're on fixed retainers with loose scope it's much less useful, and I'd rather you didn't buy it.
Freelancer here too, on the early access. In my first week it flagged a "quick landing page variant" I would have done for free. The client approved a $640 change order without blinking.
Fair question. Every approved change order is also emailed to you as a PDF, and there's a full export (JSON plus PDFs) in settings. If we ever shut down, we give at least 90 days' notice and keep exports working. That's written in our terms, not just in this comment.
Both. Any channel you add the Fenceline app to. In internal channels it only reads messages that mention a client, so your team's banter stays out of it.
This is an early-stage product
This startup is still building. Timelines can slip, and the product may change from what's described here. “Lifetime” means for as long as the founder offers the product. You can request a refund within 30 days of purchase, minus the card processing fee. After 30 days, refunds aren't available, whether or not the product ships.
Founding seats
There are only 100. Each seat is a public lifetime license. Open one to see who holds it and who held it before.
