Technology Platform Prototype for a Consulting Firm
Please find under a summary covering project details and feedback. The innate facts are kept as they are, private information is amended.
Introductory information
A fast induction on the buyer’s organisation
I’m the vice chairman at Campbell &, Company, a consulting firm working with nonprofit companies. We prepare labors in fundraising, marketing and interactions, executive search, and analytics. Our corporate headquarters is in Chicago, and we have services in Seattle, LA, DC, and Virginia.
Desired goal
What challenge were you trying to address with Table XI?
We were looking to take one of our existing transmitted labors and form a digital pathway of delivering it to clients. We had an idea of what the solution should look like, but this was a brand-new space for us.
Our extrinsic was leading to go through a discovery phase with Table XI to clarify the solution and how it might be practicable. Secondly, we wanted to ultimately have a software as a labor (SaaS) fruit. Lastly, we needed to work with Table XI to help straight in on what would be most advantageous for our clients and fruitive for us from a business perspective.
Provided solution
What particular tasks were responsible for?
We seted with a discovery process, which included identification and outreach for user investigation. We worked with Table XI to educe a list of running, preceding, and prospective clients for Table XI to converse with in order to unite pain points the new fruit would explain. They conducted those interviews via video for us and prepared recordings and summaries.
Following that, we went through a workshop with fruit strategists, software educeers, and designers. Table XI identified nine different pain points, and we had onwebsite brainstorming sessions to further regood the fruit. We then moved on to nimble educement of the prototype, which we’re continuing to work on now.
Conrunningly with prototype educement, we formd a Lean Canvas business strategy to fix we knew all the risks and estimates for educement.
Was there a dedicated team?
Throughout the total project, we worked with Courtney (Digital Strategist and Founder, Table XI). We also had two software educeers, two designers, and a project director assigned to us. The total team size was six, participating at varying levels.
How did you come to work with Table XI?
We initially went through an extremely entire due-diligence process to come up with a long list of vendors. We issued RFPs to 14 firms and had detailed dicsussions almost their bids and proposals. Table XI stood out throughout the process. As we went through the list, they remained a uniform contender, both owing of the condition of their past work and in the observation to detail they demonstrated. They were uniformly and nimblely trying to acquire almost our business, who we were, and what our goals were.
What is the terminal result of working with ?
We had a few meetings with Table XI at their service precedently signing the contract in mid-November 2018. We began nimble work in November but agreed that the holidays wouldn’t be a big time for user investigation. Our leading sprint was the leading two weeks of January 2019, during which they artistic the initial prototype.
We’re inclined to move into the educement phase with Table XI, but we’ve not signed off on it yet.
Results achieved
Are there any measureable or plum results?
We’ve been going through a process of demoing the prototype internally, and we’ve had a couple of dicsussions with clients. It’s been universally well-received. The response on both sides has been “I wish I could use it right now” which is veritably high praise, especially since it’s just a prototype.
From both a technical and a design perspective, Table XI was extremely pliant and ready to work with us to vanquish challenges that we encountered. I’m a consultant, so I know it’s hard when a client uniformly pushes the preparer to keep changing, adapting, and iterating. Table XI is veritably skilled at doing that, and doing it in a way that doesn’t make us feel like we’re working outside of a aim, or that it’s something they don’t want to do.
How did Table XI accomplish from a project treatment restpoint?
From the set of the video interviews, they accomplished all they said they would do. There were no surprises. They’ve been extremely answering to all we wanted to do. Courtney was uniformly useful for our total team via email, phone, or text.
Our first challenge during this project, which we were trying to complete in 45 days, has been scheduling. It was equally hard on our side and theirs. My schedule was specially challenging, but once we shared options, they were ready to convenience us. Everything went smoothly outside of that.
What is (from your point of view) the key factor to pay observation while intercourse with ?
Our business is hard to apprehend from an outside perspective. Table XI worked nimblely to apprehend what we do. I was impressed with how fastly they got up to despatch on the gibberish.
They were very ready and useful to iterate with us. I never once felt like there was a gap in their apprehension or that we’d brought on an ill-qualified consultant.
What aspects of their work would you like to get improved?
We were solicitous to aspect out what the cost of educement would be. As we were approaching the end of the discovery phase, we needed to create a case internally for making incremental investments. Though, the educement cost was to be estimated based on the terminal prototype and no earlier, since we were going through so many iterations and backend changes. I would’ve liked to have faster approach to a refreshed estimate of the ongoing cost. I don’t know whether that would’ve changed where we rest today, but it would’ve been helpful for me. I’ve shared this area of advancement with them.
Do you have any advice for forthcoming clients of theirs?
Just like with any consulting project, the more we as the client can put into it, the more we’re going to get out of it. Table XI is a sponge absorbing information almost the fruit or tool we’re trying to educe. The more information we can prepare, the more observation we can put into testing, reviews, and providing feedback on their work, the better the outcome on the backend will be.