03 / Redbrick x Capto: What can you build in two weeks?⌛

Well, quite a lot.

On our last week post, Laurie and Lyubomir were busy talking through the process, figuring out what happens, what doesn't, and where Capto could actually help RedBrick Accounting.
Now that we know what we're dealing with, there's only one thing left to do:
Building it! 🔨

This is where the two-week development period comes in. Or more, if the process needs it 👀
Two weeks isn't a deadline for a finished solution. It's a point we like to aim for: having the core of the business logic working, so we can put it in front of the client and test it together.

That first version doesn't necessarily include everything. For a bigger automation, it might mean getting a raw process working first, before adding all the connectors, integrations and other pieces needed for the full solution.
Why?
Because there’s only so much you can figure out on paper. Once you see the Agent working, you start seeing things differently. Maybe Laurie spots an opportunity we hadn't considered. Maybe we find another step that could be optimized. Maybe one small change makes the whole thing work even better.

And that's exactly what we want.

Rather than disappearing for months and coming back with a supposedly perfect solution, Capto and RedBrick Accounting can build, test, learn and improve together. The goal isn't just to automate the process but to keep making the solution more tailored as we learn more about it.

So now, Capto had something real to show RedBrick Accounting.
And it was Laurie's turn.
Next week, we'll see what happened when he got his hands on it. 🙌

Capto

—

Originally posted on LinkedIn:

https://lnkd.in/p/djpJndqF