Three times as many proposals, at half the unit cost.
Deetken Insight is a strategy advisory firm serving governments, public sector organizations, and private clients. Business development ran as a lifecycle, from sourcing opportunities through writing and submission to what happened after, and the slow parts were spread across all of it. We rebuilt that lifecycle with their business development team, and it has since spread to the wider consultant group.
Proposal work ate the week. A decade of past proposals and deliverables sat in files nobody could search, and the most senior consultants spent their days producing documents instead of advising clients.
- The knowledge library was siloed. It existed, but it could not be reached at the point in a pursuit where it would have been worth something.
- Nobody could see across the work. There was no single view of what was being sourced, what was being written, and what had already gone out.
- Consultant hours went on QA rather than on judgment: voice, tone, formatting and visual design, on every document.
- Limited capacity meant only a handful of RFPs could be answered each month.
A decade of past proposals and deliverables moved into one searchable place. Incoming RFPs are analyzed against that material, surfacing the relevant past work, and first drafts come back in Deetken's own tone.
Business development is a lifecycle, not a document. Deetken's runs from sourcing opportunities and judging which are worth pursuing, through writing and pre-submission compliance, to tracking what was submitted and feeding every win back into the knowledge that informs the next one. Miito sits inside that lifecycle rather than beside it, taking the time-consuming step out of each stage so the team spends its hours on the work itself.
A decade of past proposals, deliverables, consultant CVs and strategic frameworks became a single knowledge base, and answers drawn from it say where they came from. The same base is what opportunities are now assessed against, what responses are written from, and what submitted work is tracked in.
Sourcing, live pursuits, submissions and the follow-ups after them are tracked in one place, so the team can see what is being worked on rather than asking. That view is what makes the lifecycle a lifecycle rather than a series of separate scrambles.
Miito connects to SharePoint and Slack, so it fits Deetken's existing processes instead of asking the team to adopt somebody else's. Nothing had to be migrated for any of it to start working.
The add-ins put the knowledge base inside the documents themselves, so drafting, reviewing and the QA pass on voice, tone and formatting happen where the work already happens, and more than one person can be in it at once.
Output tripled without the win rate slipping, which is the part that matters: more proposals at the same standard rather than more proposals of a thinner sort. Because a response now takes a fraction of the time, consultants outside the BD team could be pulled in as writers far more often, which put subject-matter depth into proposals that used to be written without it. Revenue rose substantially on the back of that.
- Smaller opportunities became economical to pursue
- Win rate held at a 15% improvement while volume tripled
- Consultants across the firm now write, not just the BD team
We got to a point that was so good and it was picking up exactly what we wanted within our knowledge database.
We’re being called for orals and it’s great… I uploaded the RFP… please create a PowerPoint… So [it] created like this beautiful PowerPoint, it was so quick, it was amazing.
It worked like a charm… it works amazing… it actually inserted exactly in the Word document right in the spot, which is amazing.
This is amazing. Super useful, guys. These add-ins are amazing.
Tell us what your team is trying to solve.
Bring us the process your team repeats and we will shape Miito around it.
Start with one process that matters.
Deetken started with the proposal workflow. Bring us the work your team repeats and we will shape Miito around it.