Hello
You're here because we've spoken and you want to understand what working together actually looks like before you commit.
That's exactly the right instinct. This page gives you everything - the process, the timeline, what we need from you, how the system works, and the honest answers to the questions most people don't ask until later.
Take your time with it. If something's unclear or you want to talk through any of it, my details are at the bottom.
— Dani
The first thing most clients want to know is what the first month actually looks like - not the high-level version, but week by week, what happens and what's expected of them.
Below is the full engagement journey. The build phases take four to five weeks. The retainer runs from there. Step through each phase to see the detail.
The engagement journey
Claude Team · Anthropic
Your AI project. Your account.
Your data never trains the model.
anthropic.com/claude
Notion Business · Notion
Your bid database and content library.
Fully yours, always.
notion.so
Your questions answered
-
No. That's the most common starting point, and it's exactly what the migration phase is designed for. I've never walked into a firm that had its content neatly organised - if they did, they wouldn't need me.
What I do in the first week is map what you have and where it lives. Then I go and get it. Old proposals in Dropbox, CVs attached to emails, project sheets in Word documents that haven't been touched since 2021 - I pull it all into one place, clean it up, and load it into the system in a format that's actually useful.
The gap analysis is part of this. I'll flag what's missing, what's outdated, and what needs to be created from scratch - before it matters, not the night before a submission deadline.
The messier the starting point, the more dramatic the difference once the system is running. Webber's content is an asset. It's just not organised like one yet.
-
This is worth being direct about, because it's a fair concern.
The short answer is: you'll know because the system makes everything visible. Every bid, every deadline, every decision, and every piece of content lives in Notion - which means you can see exactly where things stand at any point, without having to ask me.
But visibility isn't the same as accountability, so here's what I commit to: I send a written update at the start of every bid week. I flag anything I'm waiting on before it becomes a bottleneck. I respond to messages within one business day - usually the same day. And I'm available by phone for anything urgent.
I've structured my working model specifically so that remote doesn't mean absent. The morning digest lands in your inbox before the working day starts. The Silver Review Pack arrives with enough time for a proper review, not a rushed one. Deadlines are logged in the bid register and tracked - you're not relying on me to remember them.
The studio visits are meaningful because they're intentional - discovery, training, key reviews. The remote work is effective because it's structured. Neither one is better than the other. They serve different purposes.
If something isn't working or you want more contact at any point, you tell me and I adjust. That's part of the arrangement.
-
That's exactly the scenario this system is built for. Growth is where most firms' bid processes fall apart - and expansion into a new sector like healthcare makes it more acute, not less. Healthcare procurement is a different beast. The evaluation criteria are more rigorous, the compliance requirements are more specific, and the client relationships take longer to establish. Going in with a generic proposal process won't cut it.
The system builds a healthcare-specific content layer from day one. As Webber completes healthcare projects and develops relationships in the sector, that experience gets captured properly - project sheets written to healthcare evaluation criteria, CVs that foreground relevant clinical and facility experience, methodology sections that speak the language of health infrastructure clients. By the time you're submitting your third or fourth healthcare bid, the content library reflects a firm that knows the sector, not one that's adapting general capability statements on the fly.
Beyond healthcare specifically: new staff member? Their CV goes into the people library immediately. New project completed? It's available to Claude from the next submission. New procurement portal or client type? The go/no-go criteria get updated to reflect where you're pointing the firm.
As Webber grows, the system gets better - not more complicated. And because everything is documented in the SOP, a new practice manager or business development coordinator can step into the process without a six-month learning curve.
If expansion means more bids, we adjust the retainer scope. If it means a quieter period while you're heads-down on delivery, the base covers the fixed work and we dial back. The system doesn't have a fixed gear — it moves with you.
-
That's the core problem this engagement solves, and I want to be specific about what it looks like on the other side.
For a standard bid, a principal's total involvement is roughly ninety minutes - spread across the full bid timeline, not compressed into a Sunday night. Five minutes to confirm go/no-go. Ten minutes to answer six targeted questions for the briefing note. Forty to sixty minutes to review the Silver Review Pack with track changes - reading and reacting, not writing. Thirty minutes to read the finished PDF before submission.
That's it. The methodology section, the executive summary, the project references, the team CVs, the compliance check - all of that happens without them.
What changes is not just the time. It's when the time gets spent. Reviews happen in business hours, with enough lead time to think clearly. The 11pm methodology panic stops being a thing, because there's a system that runs whether a principal is available or not.
The principals at Webber should be doing two things in the bid process: making the strategic call on whether to pursue, and approving the finished product. Everything in between is mine.
-
No. Bids don't stop because the system is being built, and I don't disappear into setup mode while live opportunities sit waiting.
If a tender lands in week two of setup, we run it. It won't have the full infrastructure behind it yet - the content library won't be complete, the Claude project will still be bedding in - but it will have me. I'll manage the bid manually, drawing on whatever content we've already migrated, and document everything I do in a way that feeds directly into the system. The bid becomes part of the build, not a distraction from it.
By the time the system is formally live, it's already been tested on real work. The first few bids aren't experiments - they're how the content library gets seeded properly and how the Claude project learns Webber's voice faster than it would from migration alone.
What this means practically: if you have something due during setup, tell me. We'll look at the timeline, work out what we have available, and run it. The retainer billing starts when the system is live - bids managed during the setup period are handled as part of the engagement, not invoiced separately as a surprise.
The five-week build timeline is for the infrastructure. The bid management starts when I do.
-
The surge model is designed specifically for this. The base retainer covers a set number of bids per month and the fixed ongoing work - monitoring, content library maintenance, pipeline reporting, check-in call. In a quiet month, that's all you pay. In a busy month, additional bids are charged at the agreed surge rate per bid type, invoiced at the end of the month.
But beyond the pricing structure, the system itself is built to flex. If Webber has a run of major government bids that require more strategic input, I increase the depth of the research and strategy phase. If you've got a quieter period and want to use the time to build out the content library or get the graphics suite properly finished, we focus there instead.
The key thing is telling me what you need. I'm not going to guess that your priorities have shifted - but if you tell me you've just won a big project and the team is heads-down on delivery for the next two months, we adjust accordingly. The retainer is a relationship, not a fixed contract deliverable.
-
This is one of the most important reasons to build a system rather than rely on a person.
Everything is documented. The SOP covers every step of the bid process. The Notion workspace is self-explanatory once you've been trained on it. The Claude project is configured and labelled so that anyone who understands the basics of AI prompting can use it.
When a new person joins - whether that's a replacement for whoever manages bids today, or a dedicated coordinator as Webber grows - the onboarding is a two-hour session, not a six-month handover. The training session from setup is recorded and available. The how-to manual covers every scenario.
This is the fundamental difference between a system and a person. People leave. Systems don't.
-
Usually because the previous attempt was a process without the infrastructure to support it. A shared folder that nobody maintained. A spreadsheet that one person updated and everyone else ignored. A template that was used twice and then abandoned.
What makes this different is that the system is designed around how bids actually work, not how you'd like them to work. The Notion database is built around the real fields you need for a proposal - not a generic project management template. The Claude project knows your firm, so using it is faster than starting from scratch. The morning digest arrives whether anyone asks for it or not.
It also helps that I'm running it with you, not handing you a set of tools and walking away. For the first three months especially, the system runs because I'm running it. By the time the engagement settles into its rhythm, using it is just how bids work at Webber - not an extra thing anyone has to remember to do.
Where to next?
You have the proposal. If there's anything you'd like to adjust - the scope, the retainer structure, the mix of services, the timeline - that's a conversation, not a complication.
Nothing in this engagement is fixed until we both agree it's right. If you want to start with a smaller footprint and build from there, we can do that. If you have a bid coming up and want to move faster than the standard timeline, we can do that too. Tell me what you need and I'll make it work.
Feel free to give me a call to discuss +61 498 179 191 or email me directly: dani@macsbidstudio.com.au