SwitchCase Studios

a Software, AI and Data Engineering studio based out of Detroit, Michigan. Making a difference for all people and businesses, one digital solution at a time.

[SwitchCase Studios @SwitchCaseStdo]

Agreed. Shared ownership is the step most teams skip until the person who set it up moves on.

[SwitchCase Studios @SwitchCaseStdo]

Links have a shelf life. On Aug 25, 2025, the https://t.co/MbMR4VuhFK links Google had flagged as inactive stopped working, and Firebase Dynamic Links shut down the same day. Somewhere, a printed QR code still points at one of them.

[SwitchCase Studios @SwitchCaseStdo]

Declaring the plan before it runs is the right instinct, and it holds downstream too. When a source schema changes, SwitchLens previews the change and maps renamed columns, so report connections stay intact. https://t.co/6jv4jUcIti

[MotherDuck @motherduck]

Flight Explainer does for flights what EXPLAIN ANALYZE does for SQL queries. See it in action!

Flights are your pipelines, run on MotherDuck. Before a flight runs, it declares its plan: the steps it will take and how they connect.

As it runs, it reports what each step did.

The result is a live chart of every run with the plan and the outcome side by side:

1/ which steps ran
2/ which way the flight branched
3/ how far each step got and what it touched.

There's nothing to install or configure. Ask your agent to "add Flight Explainer instrumentation to my flights", then ask it to show you a run. The chart opens right in your chat.

Plug into our MCP and connect your AI agent to your DuckDB data today.

Getting started is free: https://t.co/o3I78dNk0T

[SwitchCase Studios @SwitchCaseStdo]

The cheapest data breach is the field you never collected. Before a form goes live, ask of every question: what will we do with this answer? If the answer is nothing, delete it. SwitchForms can show a follow-up only when an earlier answer calls for it. https://t.co/HNz7EDRJeB

[SwitchCase Studios @SwitchCaseStdo]

@UrlPivot Agreed. A printed code is a promise that outlives the campaign, so the redirect should sit on a domain you can keep paying for.

[SwitchCase Studios @SwitchCaseStdo]

Limits stated up front are cheaper than limits discovered in production. Everything else we build is at https://t.co/IAxlA17DqQ

[SwitchCase Studios @SwitchCaseStdo]

Every launch page says fast, secure and private. Here is what our products don't do, in our own words, so you can rule us out quickly.

[SwitchCase Studios @SwitchCaseStdo]

Companion doesn't promise to be right every time. It shows its sources, holds back answers it can't support, and routes the visitor to your team.

[SwitchCase Studios @SwitchCaseStdo]

We built SimpURL around step 5. Each link keeps its destination, tags, campaign and expiration attached, so six months from now someone can still find it and tell what it was for. https://t.co/wT9NVsiwOC

[SwitchCase Studios @SwitchCaseStdo]

A 10-minute link audit for this week:
1. Search old posts, decks and packaging for short links
2. Open every one
3. Note where it points and who owns it
4. Retire the dead ones
5. Write down the ones that matter

[SwitchCase Studios @SwitchCaseStdo]

We hold ourselves to the same list. One answer, from SwitchForms: when a workspace hits its monthly response limit, new submissions pause and existing responses stay available. https://t.co/HNz7EDRJeB

[SwitchCase Studios @SwitchCaseStdo]

Arc users have until Dec 15 to request a copy of their account data, a week before the browser is sunset on Dec 22. Every tool you adopt has an exit date you don't know yet. Five questions to ask before moving in:

[SwitchCase Studios @SwitchCaseStdo]

4. Where do the backups live? If they sit next to the data, they can leave with it.
5. Who on the team would notice first?

[SwitchCase Studios @SwitchCaseStdo]

This is why Companion checks each answer against the passages it retrieved and replaces unsupported output before a visitor sees it, with a route to your team when the knowledge runs out. https://t.co/ulP9sGZV64

[SwitchCase Studios @SwitchCaseStdo]

A website chatbot told a grieving customer a bereavement fare could be claimed after travel. The airline's policy said it couldn't. The airline argued it wasn't liable for its chatbot. The tribunal called that "a remarkable submission" and ordered it to pay $812.02.

[SwitchCase Studios @SwitchCaseStdo]

The line every team with a chatbot should read: "It makes no difference whether the information comes from a static page or a chatbot." Moffatt v. Air Canada, 2024 BCCRT 149. https://t.co/eYNbbEZvmL