Kallang Reach Payments / BG-Demo – Demo
Callcompleted
Kallang Reach Payments · 2 Jan 2026 09:45
Demo of the brain on sample merchant data for Wei Ling Tan, Head of Merchant Services. She called it impressive and asked for next steps. Growth was quoted at fifty-six thousand all-in, with a proposal to follow.
What was said
What this says
As at Fri 9 Oct 2026Demo of the brain on sample merchant data for Wei Ling Tan, Head of Merchant Services. She called it impressive and asked for next steps. Growth was quoted at fifty-six thousand all-in, with a proposal to follow.
What happened: Hannah Lowe showed a merchant settlement dashboard, chat in Slack and an audit log on sample data. Wei Ling asked about filtering high-risk disputes, finance access and the custom payments system.
Customer view: Wei Ling called the demo impressive and asked what the next conversation is. She said there are no huge compliance requirements, which points to Growth rather than Enterprise.
Commercial: Sophie Ling quoted Growth tier at fifty-six thousand all-in with an eight-week implementation. The call does not show how that figure splits between subscription and implementation.
Watch: The proposal date was left at over the next few weeks. Hannah said the brain replaces manual reporting entirely, and the custom payments connector needs some data-model work.
Themes
As at Fri 9 Oct 2026Who was there
BG-Demo
Them
Follow-up
Next steps
As at Fri 9 Oct 2026- Hannah Lowe sends Wei Ling Tan a written technical note on architecture and data flow.
- Sophie Ling prepares the proposal draft covering systems, users, connectors and the eight-week timeline.
Risks
As at Fri 9 Oct 2026- The proposal date was left open at over the next few weeks, so momentum could slip.
- The custom payments system needs a bespoke connector and data-model work inside the eight-week plan.
- Hannah said the brain replaces manual reporting entirely, which may set expectations too high.
Opportunities
As at Fri 9 Oct 2026- Growth tier subscription with an eight-week implementation, quoted at fifty-six thousand all-in.
- Finance and sales views on top of merchant data could widen use beyond merchant services.
Transcript
Sophie LingHi Wei, thanks for coming back. Sophie and Hannah here. Hannah's our Solutions Engineer, she's going to walk you through the interface and show you what this looks like for merchant data. Sound good?
Wei Ling TanYeah, let's do it.
Hannah LoweRight. So I've set up a demo environment with sample merchant data: transactions, payouts, disputes. This is the search interface. You ask the brain a question...'show me all disputes by merchant for the last month', and it finds the answer across your systems. No SQL, no waiting.- Hannah LoweHere's a dashboard I've built, merchant settlement overview. You see all merchants, payout status, commission, disputes. This is what your merchant services team would see day to day.
- Wei Ling TanCan I filter this? Say, show me only high-risk disputes?
- Hannah LoweYes. That's the filter here. And you can export, share internally, or drill down into the individual merchant. Click on any merchant and you see their transaction history, payment method, chargeback rate, all from Salesforce and your payments system in one place.
- Wei Ling TanThat's clever. And your finance team can see this too?
- Hannah LoweExactly. You set up pages based on roles. Finance sees settlement and commission data from Xero plus transaction volume from your system. Sales sees merchant health and growth. Everyone sees what they need, nothing they don't.
- Sophie LingTo be precise, the data refreshes every night. By morning, all your merchant data is up to date: new transactions, new disputes, everything.
- Hannah LoweAnd here's the chat interface. Your merchant services team asks, 'which merchants haven't paid fees this month?' They ask the brain in Slack, and it answers. Drill down, refine, ask follow-ups, all in real time.
- Wei Ling TanHow does the custom payments system fit in?
- Hannah LoweWe'd build a connector to it, via API or database connection. Then it's just like Salesforce: transactions flow in, index, you can query them. We'd need to do a bit of work on the data model, but it's straightforward.
- Sophie LingAnd that's part of the eight-week implementation. Week one is connectors, including your custom system. Weeks two through eight are building dashboards and training.
- Hannah LoweHere's an audit log, every user action is tracked. Who asked what, when, what the answer was. Helps with compliance and governance.
- Wei Ling TanWe don't have huge compliance requirements, but we do track for internal audit.
- Hannah LowePerfect. So that's covered. The short answer is, this replaces your manual reporting entirely. Your team goes from 'pull data, reconcile, send Excel' to 'ask the brain, get an answer'. The longer answer is that your team starts asking questions they couldn't ask before.
- Sophie LingAnd the brain runs inside your Snowflake account, so your data stays where it is. You control it, we just query it.
- Wei Ling TanThis is impressive. What's the next conversation?
- Sophie LingWe draft a proposal: your exact systems, the user count, the connectors, eight-week timeline. We quote Growth tier at fifty-six thousand all-in. Then we talk through implementation and any questions. If it's a fit, you sign an order form.
- Wei Ling TanWhen can we do the proposal call?
- Sophie LingI can aim for over the next few weeks. That gives you time to review what you've seen, and we can address any questions the team has in between.
- Wei Ling TanThat works for me.
- Hannah LoweI'll send a technical note: what we've talked through, the architecture, data flow, all in writing.
- Sophie LingAnd I'll get the proposal draft ready over the next few weeks. Thanks very much, Wei. Cheers.
- Wei Ling TanThanks both. Cheers.