Vossberg Logistik / BB-Demo – Demo
Callcompleted
Vossberg Logistik: documents · 2025-10-29 10:15
Lena Vogel saw the brain answer a cross-system ops question in one query and called it powerful. She asked about the custom WMS, data control, uptime and extra connectors, and will take it back to Julia.
What was said
What this says
Current to 11 Oct 26Lena Vogel saw the brain answer a cross-system ops question in one query and called it powerful. She asked about the custom WMS, data control, uptime and extra connectors, and will take it back to Julia.
What happened: Hannah Lowe ran a demo on sample Salesforce, WMS and email data, built around an overdue-invoice question. Sophie Ling closed by offering a summary and a kick-off the month after the call.
Customer view: Lena reacted strongly to the single query and asked practical questions on Snowflake control, deletion, downtime, training and broken connectors. Her one open concern was the in-house WMS, which Hannah said needs schema or API access.
Commercial: The pitch was Enterprise, with 99.9% uptime, a named engineer and twenty connectors. Lena asked about adding a BI or contract tool later, which is the additional connector add-on.
Watch: Lena is taking it to Julia, whose role the evidence does not show, and nobody else from Vossberg was on the call. The evidence does not show what happened after the 29 Oct 2025 demo.
Themes
Current to 9 Oct 26Theme
Enterprise demo, custom WMS
Importance
praise
Sentiment
positive
Voice
champion
Who was there
BB-Demo
CRMmade from
Them
CRMmade from
Follow-up
Next steps
Current to 9 Oct 26- Sophie Ling to send Lena the use-case summary and timeline she promised.
- Hannah Lowe to scope the WMS connector once Vossberg IT shares the schema or API.
Risks
Current to 9 Oct 26- The in-house WMS has no standard connector, so delivery depends on Vossberg IT providing a schema or API.
- Julia, who Lena must convince, was not on the call and her role is not shown.
Opportunities
Current to 9 Oct 26- Enterprise implementation for fifty to sixty users across ops, analytics and sales.
- Additional connector add-on for a future BI or contract management system.
Transcript
Sophie Ling NoneLena, morning. Hannah's here, she's going to show you the brain running on your data. You ready?
Lena Vogel NoneLooking forward to it. You pulled actual data from our systems?
Hannah Lowe NoneWe have. Your IT team sent us samples from Salesforce, the WMS and email. I've built a test environment showing how those would integrate. This is what it would look like live.- Lena Vogel NoneOkay, great. What should I be looking for?
- Hannah Lowe NoneI want you to see how a question you'd actually ask gets answered across your systems. So let's say: show me all customers in Germany with overdue invoices that have been called in the past week. That's a real ops question, right?
- Lena Vogel NoneYeah, that's exactly what we'd want to know.
- Hannah Lowe NoneSo in your current setup, that would be manual work or a spreadsheet someone spends an afternoon building. With the brain, I ask it once and it searches your entire data history across all systems.
- Hannah Lowe NoneThere, those are your customers, their outstanding amounts, the most recent call with each one, and the notes from that call. One query.
- Lena Vogel NoneThat's one query. Wow.
- Hannah Lowe NoneAnd you can export that, build a dashboard from it, or ask follow-ups. What contracts are at risk? Who should we contact next? Those are all one search now.
- Lena Vogel NoneWho would actually use this?
- Hannah Lowe NoneYour ops leadership gets visibility without waiting for a report. Your analytics team can build dashboards without SQL. Your sales team can see account history and notes instantly. You'd probably give access to fifty, sixty people across those groups.
- Lena Vogel NoneIs it complicated to set up?
- Hannah Lowe NoneThe short answer is no, not for the users. The longer answer is we do the hard work during implementation. We write the connectors, the bridges from your systems to the brain, and test them. You point us at your systems, your IT team gives us credentials to do the sync, and we go from there.
- Lena Vogel NoneHow do you handle our WMS? That's pretty specific, is that a standard connector?
- Hannah Lowe NoneNot always. What WMS do you use?
- Lena Vogel NoneIt's a custom system, built in-house.
- Hannah Lowe NoneOkay, so custom is more complex. We'd need your team to point us at the database schema or an API. If there's an API, we can usually build a connector fairly quickly. If it's just database access, we can use that too. Either way, it's the kind of thing we solve during the implementation.
- Lena Vogel NoneAnd you're not sending our data anywhere, you said Snowflake?
- Hannah Lowe NoneRight. Your Snowflake account stays yours. The WMS data and Salesforce and email, all land in your Snowflake. We run the query layer inside Snowflake, so the queries are happening on your data, in your account. We don't copy anything to our systems.
- Lena Vogel NoneAnd if we need to delete data?
- Hannah Lowe NoneYou're in control of the Snowflake account. You can purge any table, any connector, anytime. You can also rotate API keys or revoke credentials yourself.
- Lena Vogel NoneWhat happens when you upgrade, do we have downtime?
- Hannah Lowe NoneWe do updates to the brain maybe once a month. Most are behind the scenes. If there's a user-facing change, we'd notify you and schedule it off-hours. Enterprise gets a ninety-nine point nine percent uptime SLA, basically no measurable downtime.
- Lena Vogel NoneIs there training?
- Hannah Lowe NoneYes. During implementation, we run training sessions with your ops team and your end users. You learn how to ask questions, build dashboards, troubleshoot basic issues. And we stay available, on Enterprise you get a named engineer as your support contact.
- Lena Vogel NoneHow often would I be in touch with you?
- Hannah Lowe NoneDuring the twelve weeks we're very active: calls, demos, testing. Once live, we'd check in monthly. If you hit any issues, you can ping us anytime and we aim to respond within thirty minutes on Enterprise.
- Lena Vogel NoneAnd what if a connector breaks, say the WMS changes an API?
- Hannah Lowe NoneWe monitor it. If it stops loading data, we'd spot it overnight and reach out to you and your IT team. We work together to fix it, usually a quick change on the WMS side or a connector update on ours.
- Lena Vogel NoneWhat if we want to add more systems later, say a new BI tool or a contract management system?
- Hannah Lowe NoneThat's an add-on. Enterprise includes twenty connectors. If you need a twenty-first, that's an additional connector add-on. You'd discuss that with Sophie and we'd work out the cost and timeline.
- Sophie Ling NoneUsually not a big lift if the system has an API. A few days of work for us.
- Lena Vogel NoneOkay. And the timeline, if we move forward, when would we start?
- Sophie Ling NoneWe could kick off in November if you want to move fast. That puts you live sometime in January or February, depending on the security review.
- Lena Vogel NoneI think I have enough to go back to Julia and talk through this. This is actually pretty powerful.
- Sophie Ling NoneGreat. I'll send over a summary, all the use cases we walked through, and the timeline. Anything else before we wrap?
- Lena Vogel NoneI think that's good. Thanks, Sophie, Hannah.
- Hannah Lowe NoneThanks, Lena. Speak soon.
- Sophie Ling NoneCheers, Lena.
Callsmade from