<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Works on Daniel Lemky</title>
    <link>https://daniellemky.com/work/</link>
    <description>Recent content in Works on Daniel Lemky</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <atom:link href="https://daniellemky.com/work/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Engage Spot</title>
      <link>https://daniellemky.com/work/engage-spot/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://daniellemky.com/work/engage-spot/</guid>
      <description>&lt;section class=&#34;case-section&#34; id=&#34;context&#34;&gt;&#xA;&lt;p class=&#34;case-label&#34;&gt;01 / Context&lt;/p&gt;&#xA;&lt;h2 id=&#34;one-system-for-the-work-happening-between-sundays&#34;&gt;One system for the work happening between Sundays&lt;/h2&gt;&#xA;&lt;p&gt;Church teams often piece together contact records, event registration, email, text messaging, forms, and member subscriptions across unrelated tools. The result is duplicated data and communication history that disappears into separate accounts.&lt;/p&gt;&#xA;&lt;p&gt;I founded Engage Spot to bring those workflows into one product. I have owned the work from customer discovery and product design through application architecture, deployment, billing, support, and ongoing operations.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
