Approach
How an engagement runs.
There is no menu here. There is a way of working and a set of steps, and the first one is spending time with your people before anybody writes a line of code.
The method
Understand the work. Build around it.
The order matters more than any single step. Most failed pilots were built before anybody established what was worth building.
-
Interview and shadow
We spend the first days inside the work. Partners, managers, seniors, administrators. We ask what took longest last week and what got done twice. We watch a return get assembled, a binder get built, a review get cleared. The written process and the real one are usually different, and the difference is where the work is.
-
Present our findings
We come back with a list. For each item: what it costs the firm now, what we think software does to that, how confident we are, and what it would take to build. Some of the list is things to stop doing rather than things to automate. You get the whole list, including what we ruled out and why.
-
Build it
We pick one thing and build it properly, in your environment, against your real data, under your access controls. You watch it work on your own files. When it gets something wrong, and it will, you see that too, which is the part a vendor demonstration never shows you.
-
Deploy and hand over
We get it in front of the people whose work it changes, sit with them while they use it, and fix what the first fortnight turns up. Then we write down how it works, what it costs to run, what breaks it and who in the firm owns it now.
The engagement
Ways to work together.
Each step is designed to be worth doing on its own and to make the next one easier to judge. Pricing is a conversation, because what we would charge depends on what the work turns out to be.
-
A demonstration, built for your firm
Before any money changes hands.
We build a clearly labeled demonstration using synthetic data, with your firm’s branding and a relevant example of the work. It gives you something concrete to review with your team without sharing client records.
-
Teaching your people
A course for the firm, run on your own work.
Your people are already using these tools, whether or not the firm has a policy about it. Training makes that deliberate. Where the systems are reliable, where they are not, what has to stay with a person, and how to tell the difference inside your own workflow. Sessions can run at your office or through an online course we create, custom-tailored to your firm’s work and the people learning it.
-
A two week pilot
Discovery and a small-scope solution for part of your firm.
Over two weeks, we interview and shadow your team, identify useful opportunities and build one small-scope solution. Depending on the agreed scope and your environment, the pilot is running in a workflow or demonstrated and ready for implementation. You also receive our findings and options for further work.
-
An expansion
Additional work, scoped around what you need next.
An expansion can extend the pilot, pursue another opportunity we identified, or build something different your firm needs. It does not have to follow one predetermined path. We agree on the deliverables, scope and price before the additional work begins.
-
Keeping it running
Ongoing support, for as long as it is useful.
Models change, your systems change, and the people who used it move on. Ongoing support covers the maintenance, the retraining of new staff, and the next small thing. It is optional, it is cancellable, and we would rather you needed less of it each year.
What we commit to
What you can expect from us.
-
The ownership terms are clear.
Your agreement distinguishes client-specific deliverables from reusable Redbroch components and third-party tools. We explain what your firm owns, what is licensed and how you can keep using the system.
-
The output can be traced.
Anything the system tells your people should be checkable against the document it came from. An answer that cannot be traced is an answer a reviewer cannot sign.
-
We use your existing systems where practical.
We start with the tools and environment your firm already administers. Where another service or local hardware would help, we agree on the design, access and data handling before implementation.
-
We say plainly what we have not established.
Where something is measured, we show the measurement. Where it is an estimate, we say so and show the working.
-
We say when the answer is a process change.
Some of what slows a firm down gets worse when software is added to it. We would rather tell you that in week one than build around it.
Where to start
Start with a demonstration relevant to your firm.
We would rather show you something working on synthetic examples in your firm’s language than talk about what is possible in general. Tell us what your firm does and where the work piles up, and we will come back with something to react to.