<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Jovis AI</title><link>https://blog.jovis.ai/</link><description>Recent content on Jovis AI</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Thu, 23 Jul 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://blog.jovis.ai/index.xml" rel="self" type="application/rss+xml"/><item><title>Your data team is not a search engine</title><link>https://blog.jovis.ai/posts/your-data-team-is-not-a-search-engine/</link><pubDate>Thu, 23 Jul 2026 00:00:00 +0000</pubDate><guid>https://blog.jovis.ai/posts/your-data-team-is-not-a-search-engine/</guid><description>&lt;p&gt;&amp;ldquo;Can someone pull churn by plan for the last two quarters?&amp;rdquo;&lt;/p&gt;
&lt;p&gt;It is a reasonable question. It is also the kind of question that can bounce around Slack for three days.&lt;/p&gt;
&lt;p&gt;Someone needs to find the right table. Someone else needs to explain which cancellation date counts. Finance may have a different definition of churn than customer success. By the time a chart arrives, the meeting that prompted the question has moved on.&lt;/p&gt;</description></item><item><title>The Monday question your leadership team should answer before lunch</title><link>https://blog.jovis.ai/posts/the-monday-question/</link><pubDate>Wed, 22 Jul 2026 00:00:00 +0000</pubDate><guid>https://blog.jovis.ai/posts/the-monday-question/</guid><description>&lt;p&gt;Monday meetings often start with a ritual: each function arrives with a slide, a metric, and a short explanation of why the metric is either good, not good, or complicated.&lt;/p&gt;
&lt;p&gt;The ritual is familiar because it is safe. It is also a poor way to learn what changed.&lt;/p&gt;
&lt;p&gt;The slide tells you that pipeline fell 12%. The conversation spends ten minutes debating whether the comparison should be week over week or month over month. By the time someone asks which segment moved, the meeting is nearly over and the answer is promised for later.&lt;/p&gt;</description></item><item><title>How to build an AI agent your team will actually use</title><link>https://blog.jovis.ai/posts/how-to-build-an-ai-agent-your-team-will-use/</link><pubDate>Tue, 21 Jul 2026 00:00:00 +0000</pubDate><guid>https://blog.jovis.ai/posts/how-to-build-an-ai-agent-your-team-will-use/</guid><description>&lt;p&gt;Most internal AI projects begin with a broad promise: give everyone an assistant for everything.&lt;/p&gt;
&lt;p&gt;That promise is hard to evaluate and even harder to trust. A general assistant may sound impressive in a demo, then leave people unsure what it knows, where its answers came from, or when they should use it instead of asking a colleague.&lt;/p&gt;
&lt;p&gt;The agents that get used tend to begin with a much narrower job.&lt;/p&gt;</description></item><item><title>AI needs a place in your operating model</title><link>https://blog.jovis.ai/posts/ai-needs-a-place-in-your-operating-model/</link><pubDate>Mon, 20 Jul 2026 00:00:00 +0000</pubDate><guid>https://blog.jovis.ai/posts/ai-needs-a-place-in-your-operating-model/</guid><description>&lt;p&gt;Many companies have reached the same awkward stage with AI. People have tried it. A few power users have found their favorite prompts. There is a collection of tabs, pilots, and informal habits. Nobody is quite sure which uses are safe to repeat or how a good experiment becomes normal work.&lt;/p&gt;
&lt;p&gt;Buying another chat tool rarely fixes that.&lt;/p&gt;
&lt;p&gt;The missing piece is usually an operating model. People need to know where they can ask questions, which data they can use, what an answer is based on, and who improves the system when it falls short.&lt;/p&gt;</description></item><item><title>Stop building more dashboards. Start making answers easier to find.</title><link>https://blog.jovis.ai/posts/stop-building-more-dashboards/</link><pubDate>Sun, 19 Jul 2026 00:00:00 +0000</pubDate><guid>https://blog.jovis.ai/posts/stop-building-more-dashboards/</guid><description>&lt;p&gt;Dashboards are good at one thing: putting a known set of metrics in the same place.&lt;/p&gt;
&lt;p&gt;That is useful. Every company should know how revenue, retention, pipeline, product usage, and support load are moving. The trouble begins one click after the dashboard.&lt;/p&gt;
&lt;p&gt;Revenue is down. Which customers drove it? Was the change concentrated in a product line? Did the same customers contact support more often? Did the sales cycle get longer, or did fewer opportunities enter the funnel?&lt;/p&gt;</description></item><item><title>About Me</title><link>https://blog.jovis.ai/about/</link><pubDate>Mon, 01 Jan 2024 00:00:00 +0000</pubDate><guid>https://blog.jovis.ai/about/</guid><description>&lt;p&gt;Hello! Welcome to my blog.&lt;/p&gt;
&lt;p&gt;I&amp;rsquo;m a software engineer passionate about clean design and minimalism. This site is built with Hugo and the Swiss Operator theme.&lt;/p&gt;
&lt;h2 id="contact"&gt;Contact&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://github.com/username"&gt;GitHub&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://linkedin.com/in/username"&gt;LinkedIn&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;</description></item></channel></rss>