04 / RedBrick x Capto: Then RedBrick Accounting broke it (we wanted them to!) 🙌

Last week, we left RedBrick Accounting with a working version of the process that we had been building with them. This week, it was time to put that version to the test.

And yes, this is where RedBrick Accounting gets to break it. Well, not completely.

The point of the first working version is to give RedBrick Accounting something real to use and react to. They are able to quickly test the process and give us feedback on what they would like to change, add, or remove, as well as any bugs they come across along the way.

Capto then takes that feedback back to the process and makes the necessary adjustments. Once the changes are ready, we get back in touch with Laurie and let him quickly test the updated version again. The iterative approach we take might sound simple and common sense, but this is an important piece to building something right the first time, and so it doesn’t need to be fixed constantly in the future.

Sometimes the process goes through several rounds of feedback, adjustments, and testing. There is no fixed number, because every client and every process is different. Over a longer period we also always make ourselves available to continue to enhance and improve processes.

What we are describing is probably the less glamorous part of AI & automation and not exactly the part that makes for the most exciting LinkedIn content. However, it is necessary if you want the end result to be genuinely tailored to the people who will actually use it.

At Capto, the idea is not to give every client the same tool or platform and ask them to adapt their process around it. It is much closer to being a genie in a bottle: tell us what you need, what you want changed, and what would make your life easier, and we keep refining the solution around your specific process.

Unlike a genie, you get way more than 3 wishes! (and rounds of enhancement) So the cycle continues: RedBrick Accounting tests the process, Capto collects the feedback and makes the adjustments, and RedBrick Accounting tests it again. Which is exactly what we want, because sustainable and ROI generating deployments almost never stay the same from Day 1.

Capto

—

Originally posted on LinkedIn:

https://www.linkedin.com/posts/wearecapto_04-then-redbrick-accounting-broke-it-we-activity-7508524278468907009-Sbxx?