Your first 90 days with F*IT.
Switching to a new system is the part everyone glosses over. Here's exactly what the first 90 days look like - week by week, what we do, what you do, and what to expect when something doesn't go to plan.
Most software companies sell you the destination and skip the journey. We're going to do the opposite. The migration is where the value is created or destroyed, and most tradies have been burned before, so this is what actually happens, in plain English.
Onboarding is the riskiest part of any platform switch. It's also the most under-talked-about. Vendors love showing you the polished dashboard and the impressive feature list. They tend to skip past the part where you're supposed to migrate three years of customer data, learn a new system, and not lose any leads in the process.
F*IT's first 90 days are deliberately designed around that risk. Three phases, each with a specific job. By day 90 you're fully running, your old stack is cancelled, and you're getting hours back every week. Here's how we get there.
// the shape of the journeyThree phases. Three jobs.
Each phase has one focus. We don't try to do everything at once, that's how things break. By the end of each phase, a specific set of things are working, locked in, and not at risk. Then we move on.
The week-one sprint where everything turns on
The first month is heavy lift on our side, light lift on yours. Within the first 14 days we're plugged into your existing systems, your data is migrated, your AI agents are trained on your business context, your phone receptionist is live, and your new website is built. None of that requires you to learn a new tool yet, it requires you to give us answers about your business, then let us do the work.
By the end of week one your tenant is provisioned, your brand is loaded (logo, colours, voice, services list, suburbs you cover), and your existing data is migrated from whatever CRM or job management tool you're moving from. By end of week two, your AI receptionist is taking calls on a tracked number, your website is live on your domain, and your core agents are running in draft mode for everything outbound.
That last bit is important. Drafts only. Nothing goes out the door without your approval for the entire first month. You're driving every car the system builds. That's deliberate, it lets you correct early, often, and without consequence. Every correction sharpens the system.
- Phone receptionist live, capturing every inbound call in your voice
- SEO-built website live on your domain, pages scoped to your tier and trade
- Customer + job data fully migrated from old system
- Stripe Connect wired, invoices flowing
- Core agents trained on your business - pricing rules, brand voice, escalation thresholds
- Compliance vault populated, SWMS templates set up
- Daily review rhythm established - you check, approve, correct, repeat
The month where you start trusting the system
Month one is about getting things running. Month two is about tuning them so they run well. By now the agents have a few hundred data points from your corrections, you've seen them handle a few hundred routine interactions correctly, and you're starting to notice the things you used to do that you no longer have to.
This is the phase where most owners promote agents from L1 (drafts only) to L2 (auto with review) for the routine stuff. Quote drafts that match your usual patterns start sending without manual approval, with you able to recall or override within a window. Review requests fire automatically after job completion. Social posts publish on your schedule. The repetitive stuff drops off your plate first, in deliberate increments.
Time in the platform drops from month one, most owners are now spending around 30 to 45 minutes a day, and that time is shifting from doing the work to checking the work was done right. By the end of month two, you're spending more time looking at your dashboard for insights than for tasks.
- Routine quotes auto-send (with override window) - most quote drafts no longer wait on you
- Review requests automate post-job completion
- Content rhythm establishes - social posts going out reliably
- Local ranking baseline locked in, first month of trend data
- Compliance reminders flowing on schedule
- You start seeing weekly time savings - typically 4 to 8 hours a week recovered
The month where you stop thinking about it
Month three is the one nobody warns you about with most platforms because most platforms don't reach it. By day 90, F*IT has handled hundreds of your customer interactions, drafted a few weeks of your content, built and ranked some of your service pages, and gathered enough operational data to start surfacing insights you couldn't easily get before.
This is also the point where most owners stop checking the platform daily. You drop to a couple of times a week, once to approve flagged escalations, once to look at the weekly summary. The rest runs on its own. Hours recovered hit 8 to 12 a week for most owners. The conversation with us shifts from "is everything working" to "what should we tune next."
By day 90, your old stack is cancelled. The shadow phase is over, you're not running ServiceM8 alongside F*IT, or Hootsuite alongside The Mouth, or BrightLocal alongside The Watcher. You're paying one bill, getting one set of insights, and the back office runs without you.
- Old tools cancelled, single subscription replacing the lot
- Most agents running at L2 or L3 autonomy depending on category
- Weekly time saved holding steady at 8 to 12 hours
- Owner Command Centre is your morning + evening read, not a workplace
- First measurable lift in inbound enquiries, rankings, or repeat business showing up
- Conversations with us shift from "fixing things" to "growth tuning"
You're not hands-off.
This is the part that gets glossed over in marketing. F*IT runs autonomously, but it doesn't set up autonomously. The first 30 days require real time from you. Not endless, but real.
Realistic time commitment from your side, broken down by phase:
Front-loaded discovery, 1 to 2 hours, once. Before month one really kicks off, we need a handful of answers from you that only you can give. Pricing rules, services list, brand voice, your standard quote terms, the suburbs you cover, your escalation thresholds. This is the heaviest single block of input you'll do, and it's a one-shot deal. Most owners knock it out across two or three sittings in the first few days. Done well, this is what makes the rest of the system feel like yours and not a generic template.
Month 1: ~1 hour a day. Most of this is reviewing drafts going out the door, quotes, replies, social posts, follow-ups, and correcting the agents when they get something wrong. Highest-touch month. Anyone selling you a platform that doesn't need this much input is selling you a platform that won't actually work for your specific business.
Month 2: 30 to 45 minutes a day. The corrections are getting fewer. The agents have your patterns. You're shifting from teaching to checking.
Month 3 onwards: about 30 minutes a day. You're checking what jobs are on, adding notes, confirming work is done, and approving the handful of things flagged for your judgement. Honest version: the admin hurdle never disappears entirely. There's no way around it. What changes is that 30 minutes replaces what used to be five or ten hours a week, and the work that's left is the work you're actually paid to think about.
The first 30 days are intense. They're also the only intense days. By day 90 you're spending less time on your back office than you ever have, and the system runs cleanly because you put the work in early to make it yours.
This is a different deal than most software you've used. With most software, you sign up, fumble through it for months, never quite get full value, and eventually cancel because it never clicked. F*IT's onboarding is heavy on purpose, so the rest of the time isn't.
What if it doesn't work?
Honest answer: sometimes it doesn't, at least not at first. Here's what that actually looks like, and what we do about it.
An agent gets something wrong
This will happen. Probably in the first two weeks. An AI-drafted quote will have the wrong line item. An auto-reply will hit the wrong tone. The receptionist will miss a nuance you wish it had caught. This is recoverable, and it's the point of L1 mode. You catch it before it goes out, you correct the rule, and it doesn't happen again. Most of the friction in the first month is exactly this kind of small correction, and every one makes the system sharper.
The migration hits a snag
Sometimes the data from an old system doesn't map cleanly. A custom field doesn't have a home. A workflow you relied on doesn't exist in F*IT yet. We tell you upfront when we hit this, and we work it out together, sometimes that means a workaround, sometimes it means we build something. Either way, no surprises buried in a help ticket.
You decide it's not for you
Genuinely possible. Maybe the autonomy levels don't suit how you want to run things. Maybe the platform isn't a fit for your trade. We'd rather know early than late. If you decide in the first 60 days that F*IT isn't right, we'll help you migrate your data out cleanly, not hold it hostage. The point is to find out fast whether this is going to work for you, not to lock you into something that isn't.
The honest version is: most platform migrations fail because nobody plans for the moments when things don't go to plan. We plan for them. The phased rollout, the L1-first default, the "tell us early when something's off" cadence, they all exist because the failure modes are predictable, and the only real way to handle them is to expect them.
By day 90, you're not the same business you were on day 1. The trade you do is the same. What's changed is everything around it.