ANNA: Thanks for joining. Today we must decide how to handle registration and tracking. We have three options: use a third-party service, build a simple in-house tool, or combine both in a hybrid approach. Let’s compare the pros and cons. Ben, can you start?
BEN: Sure. A third-party service is quick to launch and has reliable support, but licensing fees can be high and customization is limited.
CLARA: From a budget view, the third-party costs worry me the licensing fees are ongoing. Building in-house has higher initial costs but lower recurring costs.
DAVID: Operationally, a hybrid might give us the best of both worlds: use third-party for registration and our own system for tracking. That reduces vendor dependency but adds integration work.
BEN: A key risk with building in-house is time, we could miss our timeline. However, if we scope the in-house tool narrowly, it may be feasible.
CLARA: I’m leaning to hybrid, but I need clear cost estimates and timelines. Can we agree that whoever supports the decision will produce a short comparison table with costs, time, and risks?
ANNA: Good idea. Do we have a preference now? David seems to prefer hybrid, Ben worries about time, and Clara needs costs. Let’s confirm: Ben will prepare a one-page comparison with estimated costs and timeline by Thursday; Clara will draft a provisional budget; David will draft integration notes. We’ll reconvene Friday to confirm. Any objections?  No? Decision confirmed.