<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Tyr Xargaar</title>
    <description>The latest articles on DEV Community by Tyr Xargaar (@tyrxargaar).</description>
    <link>https://dev.to/tyrxargaar</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4182513%2Fbae6f7fa-06f5-4b66-8afe-c242aa429987.png</url>
      <title>DEV Community: Tyr Xargaar</title>
      <link>https://dev.to/tyrxargaar</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/tyrxargaar"/>
    <language>en</language>
    <item>
      <title>How to photograph a job site for a quote without emailing 12 MB files</title>
      <dc:creator>Tyr Xargaar</dc:creator>
      <pubDate>Tue, 13 Oct 2026 21:42:30 +0000</pubDate>
      <link>https://dev.to/tyrxargaar/how-to-photograph-a-job-site-for-a-quote-without-emailing-12-mb-files-21gb</link>
      <guid>https://dev.to/tyrxargaar/how-to-photograph-a-job-site-for-a-quote-without-emailing-12-mb-files-21gb</guid>
      <description>&lt;p&gt;When a contractor quotes a repair, the photos matter. They show the customer what you saw, and they protect you later if someone asks what the wall looked like before you started. But phone photos create two practical problems: they are huge, and they often contain more than you meant to share.&lt;/p&gt;

&lt;h2&gt;
  
  
  Take photos that support the quote
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;One wide shot, then close-ups.&lt;/strong&gt; The wide shot shows where the problem is. The close-up shows what it is.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Put something in the frame for scale&lt;/strong&gt;, like a tape measure or a hand.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Shoot the same angle before and after&lt;/strong&gt; so the change is obvious.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Keep the number small.&lt;/strong&gt; Six clear photos beat forty similar ones.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Shrink them before sending
&lt;/h2&gt;

&lt;p&gt;A modern phone photo is often several MB. Four of them can bounce an email or choke a text message on a weak connection. Resizing to a width of around 1600 pixels keeps them readable on a phone and brings each one down to a few hundred KB. Most phones and free desktop tools can do this, and the quote tool you use should do it for you.&lt;/p&gt;

&lt;h2&gt;
  
  
  Check what is in the picture
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Photos can carry location data in their metadata. Strip it if you share outside the job.&lt;/li&gt;
&lt;li&gt;Look for the customer's mail, documents, family photos and screens in the background.&lt;/li&gt;
&lt;li&gt;Keep job photos private to the job. A public link to an image is a link anyone can forward.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Tie the photos to the estimate
&lt;/h2&gt;

&lt;p&gt;The best place for the photos is the estimate itself, so the customer approves the work with the evidence next to the price. One record per job also means you can find the pictures again when a change order comes up.&lt;/p&gt;

&lt;p&gt;I build &lt;a href="https://changesnap.onrender.com/" rel="noopener noreferrer"&gt;JobNeatly&lt;/a&gt;, which lets you attach resized private photos to an estimate and send it as a link the customer can sign from their phone. Estimates are free; the first three approvals are free, then $9 per approval or $19 a month. It does not send automatic reminders. (Disclosure: I'm the maker.)&lt;/p&gt;

&lt;p&gt;What do you photograph that most people forget?&lt;/p&gt;

</description>
      <category>webdev</category>
      <category>ux</category>
    </item>
    <item>
      <title>How to write a change order that customers actually sign</title>
      <dc:creator>Tyr Xargaar</dc:creator>
      <pubDate>Tue, 13 Oct 2026 15:11:39 +0000</pubDate>
      <link>https://dev.to/tyrxargaar/how-to-write-a-change-order-that-customers-actually-sign-3h4n</link>
      <guid>https://dev.to/tyrxargaar/how-to-write-a-change-order-that-customers-actually-sign-3h4n</guid>
      <description>&lt;p&gt;Every contractor has lived this: the job is half done, the customer says "while you're at it, can you also...", you say sure, and three weeks later you are arguing about a bill nobody agreed to in writing.&lt;/p&gt;

&lt;p&gt;A change order fixes that. It is a short written record that the scope or price changed, and that the customer said yes. Here is how to do it well without turning it into paperwork.&lt;/p&gt;

&lt;h2&gt;
  
  
  What a change order must contain
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;What changed.&lt;/strong&gt; One or two plain sentences. "Add two outlets on the east wall of the kitchen."&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;What it costs.&lt;/strong&gt; A number, not "a few hundred." Split labor and materials if you can.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;What it does to the schedule.&lt;/strong&gt; "Adds one day." Even "no change" is worth writing.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;A reference to the original job.&lt;/strong&gt; Quote number, address, or date, so it can be matched later.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;A yes from the customer.&lt;/strong&gt; A signature, a typed name, or a tap on an approval link. Something with a date on it.&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  When to write one
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;The customer asks for anything not in the original quote.&lt;/li&gt;
&lt;li&gt;You find a hidden problem (rot, old wiring, a wall that is not where the plans say).&lt;/li&gt;
&lt;li&gt;Material prices or availability force a substitution.&lt;/li&gt;
&lt;li&gt;The job gets cheaper. Credits count too, and customers remember who offered them.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;A simple rule: if you would be annoyed to eat the cost, write it down before you start.&lt;/p&gt;

&lt;h2&gt;
  
  
  Get the approval before the work, not after
&lt;/h2&gt;

&lt;p&gt;The most common failure is doing the extra work first and asking later. Customers are happiest to say yes while you are standing in front of the problem. Send the change order from your phone right then, with a photo of the issue attached. Then keep working.&lt;/p&gt;

&lt;h2&gt;
  
  
  Keep a photo trail
&lt;/h2&gt;

&lt;p&gt;A photo of the problem, dated, next to the change order closes most disputes. Take one before you touch anything.&lt;/p&gt;

&lt;h2&gt;
  
  
  Tools
&lt;/h2&gt;

&lt;p&gt;You can do all of this with a notes app and a text message. If you want it faster, I built &lt;a href="https://changesnap.onrender.com/" rel="noopener noreferrer"&gt;JobNeatly&lt;/a&gt;, a tool (free to start) that makes estimates and change orders, sends the customer an approval link, and keeps the signed record. It does not take payments or send anything to your customers on its own. You send the link yourself.&lt;/p&gt;

&lt;p&gt;I am the maker, so weigh that. The template above works with or without it. What is the change order situation that cost you the most? I would like to hear it in the comments.&lt;/p&gt;

</description>
      <category>business</category>
      <category>tutorial</category>
      <category>productivity</category>
    </item>
    <item>
      <title>A signable estimate link beats a PDF attachment: what changed for small contractors</title>
      <dc:creator>Tyr Xargaar</dc:creator>
      <pubDate>Tue, 13 Oct 2026 15:06:55 +0000</pubDate>
      <link>https://dev.to/tyrxargaar/a-signable-estimate-link-beats-a-pdf-attachment-what-changed-for-small-contractors-10fc</link>
      <guid>https://dev.to/tyrxargaar/a-signable-estimate-link-beats-a-pdf-attachment-what-changed-for-small-contractors-10fc</guid>
      <description>&lt;p&gt;I build a small web tool for contractors and trades, so I spend a lot of time on one boring question: how does a customer say "yes" to an estimate?&lt;/p&gt;

&lt;p&gt;Most small contractors still do this one of three ways: a PDF in an email, a photo of a handwritten sheet in a text message, or a verbal "sounds good". All three have the same problem. When the job changes halfway through (a change order), nobody can say later what was actually agreed.&lt;/p&gt;

&lt;h2&gt;
  
  
  What goes wrong with the PDF-in-email flow
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;The customer opens it on a phone, can't sign it, and replies "ok" in a message instead.&lt;/li&gt;
&lt;li&gt;The contractor prints it, signs it, scans it, and sends it back. Nobody does this twice.&lt;/li&gt;
&lt;li&gt;A change order lives in a different thread from the original estimate.&lt;/li&gt;
&lt;li&gt;Photos of the site are 12 MB each and bounce from the inbox.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  What a better flow needs
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;A link, not an attachment.&lt;/strong&gt; The customer taps a link on their phone and sees the estimate. No app, no account.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Sign on the same screen.&lt;/strong&gt; If approval takes more than one tap and a signature, many customers just won't bother.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;One record per job.&lt;/strong&gt; The original estimate, each change order and the approvals sit together, so "what did we agree" has a single answer.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Photos resized before sending.&lt;/strong&gt; Phone photos should be shrunk to something reasonable. Keep them private to the job, not on a public URL.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Honest limits.&lt;/strong&gt; A signed link is a clear record of who approved what and when. It is not a substitute for legal advice on a large contract.&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  What I built
&lt;/h2&gt;

&lt;p&gt;&lt;a href="https://changesnap.onrender.com/" rel="noopener noreferrer"&gt;JobNeatly&lt;/a&gt; is my attempt at this. You create an estimate, send the customer a link, and they review and sign it from their phone without an app or account. Estimates are free. The first three approvals are free, then it is $9 per approval or $19 a month. It also handles your own PDFs for signing, a manual visit planner and follow-up notes. It does not send automatic reminders or sync calendars, and I would rather say that up front.&lt;/p&gt;

&lt;p&gt;(Disclosure: I'm the maker.)&lt;/p&gt;

&lt;h2&gt;
  
  
  Question for you
&lt;/h2&gt;

&lt;p&gt;If you have built signing or approval flows, what was the thing that surprised you? For me it was how much customers prefer tapping a link over anything that looks like a form. I'd like to hear what worked for you, and what you would add for a trades audience.&lt;/p&gt;

</description>
      <category>webdev</category>
      <category>ux</category>
    </item>
  </channel>
</rss>
