<?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: Muhammad Najam Ul Hassan</title>
    <description>The latest articles on DEV Community by Muhammad Najam Ul Hassan (@itsnajam).</description>
    <link>https://dev.to/itsnajam</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%2F4218176%2Fa6d327bc-91d0-47f4-88cb-c0f5dd759b26.jpg</url>
      <title>DEV Community: Muhammad Najam Ul Hassan</title>
      <link>https://dev.to/itsnajam</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/itsnajam"/>
    <language>en</language>
    <item>
      <title>What does AI app development cost?</title>
      <dc:creator>Muhammad Najam Ul Hassan</dc:creator>
      <pubDate>Thu, 19 Nov 2026 06:50:47 +0000</pubDate>
      <link>https://dev.to/itsnajam/what-does-ai-app-development-cost-1ed3</link>
      <guid>https://dev.to/itsnajam/what-does-ai-app-development-cost-1ed3</guid>
      <description>&lt;p&gt;I finish apps people started with Claude, Cursor, Lovable or Bolt, and I build new software with AI agents doing the drafting while I own the result. This is the same guide that lives on my site, including the parts where AI is the wrong answer.&lt;/p&gt;

&lt;p&gt;AI makes the typing faster. It does not write the plan, open the accounts or test what happens when a booking arrives with no signal. There is no single AI app development cost: small jobs start at $49, a full app is one fixed price quoted after a free call, and the number is set by the same things as any other build.&lt;/p&gt;

&lt;p&gt;Short answer:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;AI makes the middle of a build cheaper: screens, plumbing, tests and the repetitive parts.&lt;/li&gt;
&lt;li&gt;The plan, your data, payments, admin screens, the store rules and testing still set the price.&lt;/li&gt;
&lt;li&gt;I quote one fixed price after a free call, the same as any other build. Small jobs start at $49.&lt;/li&gt;
&lt;li&gt;The model bill is a separate running cost, and for most business features it is small.&lt;/li&gt;
&lt;/ul&gt;

&lt;h4&gt;
  
  
  Why is there no single AI app development cost?
&lt;/h4&gt;

&lt;p&gt;AI app development cost depends on the same things as any other build, with one change: the typing gets faster while the deciding stays the same. The middle of the build, meaning the screens, form handling, plumbing between services, tests and repetitive parts, is cheaper. The edges, meaning the plan, your data, payments, the store rules and the testing that needs someone who knows your business, are roughly unchanged.&lt;/p&gt;

&lt;p&gt;That is not a small difference. It is how a repair estimated at 100+ hours became a 7-day rebuild, live on iOS and Android. That was a mobile app rebuild rather than an AI project, and it is worth being precise about: AI helped with the typing. It did not write the plan, and it did not know what happens when a booking arrives with no signal.&lt;/p&gt;

&lt;h4&gt;
  
  
  What does AI change, and what does it not?
&lt;/h4&gt;

&lt;p&gt;This is the split I use when quoting an AI-assisted build.&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;The work&lt;/th&gt;
&lt;th&gt;What AI changes&lt;/th&gt;
&lt;th&gt;What still sets the price&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;The plan&lt;/td&gt;
&lt;td&gt;Very little&lt;/td&gt;
&lt;td&gt;Someone deciding what the app must do, and what it must never do&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Screen building&lt;/td&gt;
&lt;td&gt;A lot faster&lt;/td&gt;
&lt;td&gt;How many screens, and how different they are&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Data model&lt;/td&gt;
&lt;td&gt;Some help&lt;/td&gt;
&lt;td&gt;Getting the relationships right before anything is built&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Payments&lt;/td&gt;
&lt;td&gt;Boilerplate is quicker&lt;/td&gt;
&lt;td&gt;Refunds, failures, payouts and receipts&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Admin screens&lt;/td&gt;
&lt;td&gt;Faster&lt;/td&gt;
&lt;td&gt;Who needs to see what, and who may change it&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Integrations&lt;/td&gt;
&lt;td&gt;Some help&lt;/td&gt;
&lt;td&gt;What each system expects, and what happens when it is down&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Testing&lt;/td&gt;
&lt;td&gt;Faster to write&lt;/td&gt;
&lt;td&gt;Testing the awkward cases, on a real phone and a slow connection&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;The stores&lt;/td&gt;
&lt;td&gt;Very little&lt;/td&gt;
&lt;td&gt;Apple and Google rules, screenshots, privacy answers and the wait for approval&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;After launch&lt;/td&gt;
&lt;td&gt;Very little&lt;/td&gt;
&lt;td&gt;Someone to fix it when a feed stops or a payment fails&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;Read the third column, not the second. The second is what every AI pitch talks about; the third is what you pay for, and where two quotes on the same brief differ.&lt;/p&gt;

&lt;p&gt;The data model row is the one to protect hardest. Getting the relationships wrong is cheap to do and expensive to undo: every screen, report and integration on top inherits the mistake.&lt;/p&gt;

&lt;h4&gt;
  
  
  How do you price an AI-assisted build?
&lt;/h4&gt;

&lt;p&gt;The same way I price any other build: a free call, a written plan of what I will build and what it will not do, then one fixed price. The price does not move unless the work does.&lt;/p&gt;

&lt;p&gt;There is no AI discount and no AI surcharge. If AI saves time, that time goes into testing and into the parts of your business a model cannot see. Small jobs still start at $49.&lt;/p&gt;

&lt;p&gt;Charging less for typing faster would mean discounting the part of the job that was never the risk, and pushing the saved hours out of the build instead of into the checks.&lt;/p&gt;

&lt;h4&gt;
  
  
  What does it cost to run an AI feature?
&lt;/h4&gt;

&lt;p&gt;Building it and running it are two different bills. The build is my fixed price. The running bill is the model provider's, and it follows usage.&lt;/p&gt;

&lt;p&gt;For most small business features this is dollars a month, not thousands. It becomes a real cost when every user action calls a large model, or when every call sends a long document. I work the monthly number out from published prices and your expected volume before I build, so it is not a surprise.&lt;/p&gt;

&lt;p&gt;Four things decide that number:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;How many calls a day, and what each call sends.&lt;/li&gt;
&lt;li&gt;Which model, because the price per token varies widely between them.&lt;/li&gt;
&lt;li&gt;Whether results can be cached instead of asked for again.&lt;/li&gt;
&lt;li&gt;What happens on a retry, so a failed call does not quietly double the bill.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The last one is the quiet failure: a retry loop with no cap turns one bad afternoon into an invoice.&lt;/p&gt;

&lt;h4&gt;
  
  
  How much does it cost to build an app with Claude Code?
&lt;/h4&gt;

&lt;p&gt;Claude Code is one of the tools I use, not a product you buy from me. Its own subscription or API bill belongs to whoever runs it, and it is small compared with the build.&lt;/p&gt;

&lt;p&gt;What you pay for is the plan, the data model, the parts a model cannot decide, the testing and the launch. A price per screen because an agent typed it is either a guess or a quote with the testing left out.&lt;/p&gt;

&lt;h4&gt;
  
  
  When is AI the wrong way to build it?
&lt;/h4&gt;

&lt;p&gt;Often, for part of the job. These are the cases where I lean on it least.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Rules that live in someone's head, where the model has nothing to read.&lt;/li&gt;
&lt;li&gt;Anything where a wrong answer moves money and nobody is checking.&lt;/li&gt;
&lt;li&gt;Heavy offline use, where the app has to work with no signal.&lt;/li&gt;
&lt;li&gt;A design that has to be exactly right, screen by screen.&lt;/li&gt;
&lt;li&gt;Old systems with no documentation and no test environment.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;None of those rules out AI assistance. It belongs on the repetitive parts while a person owns the part that can hurt you.&lt;/p&gt;

&lt;h4&gt;
  
  
  How do I compare two AI-assisted quotes?
&lt;/h4&gt;

&lt;p&gt;Send the same brief to both, and compare what is included before you compare the numbers.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;What each quote includes, especially testing and the store submission.&lt;/li&gt;
&lt;li&gt;Who owns the accounts, the code and the data.&lt;/li&gt;
&lt;li&gt;What the monthly running bill is expected to be, and who pays it.&lt;/li&gt;
&lt;li&gt;What the fix-it promise covers after launch.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;A cheaper quote is usually a shorter list, not a better deal. The written plan is what makes two quotes comparable.&lt;/p&gt;

&lt;p&gt;Takeaways:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;AI cuts the typing, not the deciding.&lt;/li&gt;
&lt;li&gt;Scope, money, admin, integrations and the stores still set the price.&lt;/li&gt;
&lt;li&gt;The model bill is separate, and small for most business features.&lt;/li&gt;
&lt;li&gt;Ask what is included before you compare two numbers.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Q: How much does it cost to build an app with AI?&lt;br&gt;
A: There is no single number, because the price follows what the app has to do. Small jobs start at $49, and a full app is quoted as one fixed price after a free call. AI lowers the typing time. It does not remove the plan, the data, the payments, the testing or the store submission, and those are what the price is made of.&lt;/p&gt;

&lt;p&gt;Q: Can I build an app with AI for free?&lt;br&gt;
A: You can get something that looks like an app for free. What costs money is everything around it: the accounts, the data, the payments, the testing and getting it into the stores. If you want to try that route first, the &lt;a href="https://najam.dev/guides/app-builder-or-developer/" rel="noopener noreferrer"&gt;app builder guide&lt;/a&gt; covers when a builder is enough and when it is not.&lt;/p&gt;

&lt;p&gt;Q: Does my app need AI at all?&lt;br&gt;
A: Often no. Most of what I build is ordinary software with a database. AI earns its place on a narrow job, like sorting enquiries, reading documents or drafting something a person approves. I will tell you on the call if it does not belong in yours.&lt;/p&gt;

&lt;p&gt;Sources:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Claude Code documentation: &lt;a href="https://docs.claude.com/en/docs/claude-code/overview" rel="noopener noreferrer"&gt;https://docs.claude.com/en/docs/claude-code/overview&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;Claude pricing: &lt;a href="https://claude.com/pricing" rel="noopener noreferrer"&gt;https://claude.com/pricing&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;Apple Developer Program: &lt;a href="https://developer.apple.com/programs/" rel="noopener noreferrer"&gt;https://developer.apple.com/programs/&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;Google Play Console registration: &lt;a href="https://support.google.com/googleplay/android-developer/answer/6112435" rel="noopener noreferrer"&gt;https://support.google.com/googleplay/android-developer/answer/6112435&lt;/a&gt;
&lt;/li&gt;
&lt;/ul&gt;




&lt;p&gt;The full guide, with its sources, is at &lt;a href="https://najam.dev/guides/ai-app-development-cost/" rel="noopener noreferrer"&gt;https://najam.dev/guides/ai-app-development-cost/&lt;/a&gt;. If you want the short version of how I work: one engineer, one fixed price agreed in writing before anything starts, and the code and the accounts stay in your name. More at &lt;a href="https://najam.dev" rel="noopener noreferrer"&gt;https://najam.dev&lt;/a&gt;&lt;/p&gt;

</description>
      <category>ai</category>
      <category>webdev</category>
      <category>programming</category>
      <category>productivity</category>
    </item>
    <item>
      <title>Dashboard or spreadsheet: the honest test for when you need software</title>
      <dc:creator>Muhammad Najam Ul Hassan</dc:creator>
      <pubDate>Wed, 18 Nov 2026 08:28:20 +0000</pubDate>
      <link>https://dev.to/itsnajam/dashboard-or-spreadsheet-the-honest-test-for-when-you-need-software-541g</link>
      <guid>https://dev.to/itsnajam/dashboard-or-spreadsheet-the-honest-test-for-when-you-need-software-541g</guid>
      <description>&lt;p&gt;I build apps, websites and automation for small businesses and founders, and most of the internal tools I build replace something that started as a perfectly sensible file. This is the same guide that lives on my site.&lt;/p&gt;

&lt;p&gt;Spreadsheets are not the problem. The problem is the moment one becomes the only record of what your business did, and nobody dares to edit it. Keep the file while one person reads it and the numbers still match reality. Replace it when two people edit the same file, or when a total is wrong and nobody can say why.&lt;/p&gt;

&lt;p&gt;Short answer:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Keep the spreadsheet while one person reads it and the numbers still match reality.&lt;/li&gt;
&lt;li&gt;Replace it when two people edit the same file, or when a total is wrong and nobody can say why.&lt;/li&gt;
&lt;li&gt;A dashboard is trusted only when every figure traces back to the rows behind it.&lt;/li&gt;
&lt;li&gt;The usual first step is not a big system. It is one screen and one source of truth.&lt;/li&gt;
&lt;/ul&gt;

&lt;h4&gt;
  
  
  What are the signs it has outgrown the spreadsheet?
&lt;/h4&gt;

&lt;p&gt;These are the ones I see, in roughly the order they arrive.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Two people edit the same file, and one of them overwrites the other.&lt;/li&gt;
&lt;li&gt;There is a copy on someone's phone that is more up to date than the shared one.&lt;/li&gt;
&lt;li&gt;A formula broke and nobody noticed for a week.&lt;/li&gt;
&lt;li&gt;You cannot tell who changed a number, or when.&lt;/li&gt;
&lt;li&gt;Adding a column means rebuilding three tabs and the summary.&lt;/li&gt;
&lt;li&gt;The person who understands it is the person you cannot afford to lose.&lt;/li&gt;
&lt;li&gt;A manager asks a question and the answer takes someone an hour to build.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;None of those is about the size of the file. A small spreadsheet with three editors is already past the point where a file is the right tool, and a large one with a single careful owner can be fine for years.&lt;/p&gt;

&lt;p&gt;The last two are the expensive ones. When answering a question costs an hour of somebody's time, the file is charging you a salary to do what a screen would do in a second. When only one person understands it, you are carrying a risk that has nothing to do with software.&lt;/p&gt;

&lt;h4&gt;
  
  
  What does a dashboard give you that a file does not?
&lt;/h4&gt;

&lt;p&gt;Three things: one source of truth, roles, and a screen that loads on a phone in a warehouse or a cab.&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;What you need&lt;/th&gt;
&lt;th&gt;Spreadsheet&lt;/th&gt;
&lt;th&gt;A built dashboard&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;One number everyone agrees on&lt;/td&gt;
&lt;td&gt;Only if one person owns the file&lt;/td&gt;
&lt;td&gt;Yes, from one source&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Two people editing at once&lt;/td&gt;
&lt;td&gt;Conflicts and overwrites&lt;/td&gt;
&lt;td&gt;Handled properly&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Who changed what, and when&lt;/td&gt;
&lt;td&gt;Rarely, and never reliably&lt;/td&gt;
&lt;td&gt;Every change is recorded&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Different views for different roles&lt;/td&gt;
&lt;td&gt;Tabs, and trust&lt;/td&gt;
&lt;td&gt;Real access control&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Readable on a phone on site&lt;/td&gt;
&lt;td&gt;Poorly&lt;/td&gt;
&lt;td&gt;Designed for it&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Feeds itself from your shop, bank or jobs&lt;/td&gt;
&lt;td&gt;By hand, or by a fragile link&lt;/td&gt;
&lt;td&gt;By a connection that can be monitored&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Cost to start&lt;/td&gt;
&lt;td&gt;Nothing&lt;/td&gt;
&lt;td&gt;A build, then very little to run&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;The row that decides most projects is the last one before cost. A file gets its numbers from a person remembering to paste them. A built screen gets them from a connection, and a connection can be monitored, so you find out it stopped sending on the day it stopped rather than at the end of the month.&lt;/p&gt;

&lt;p&gt;The row about roles is the one people underestimate. Tabs and trust are not access control. If a number should only be visible to the owner, that has to be enforced where the data is read, not by asking people to stay off a tab.&lt;/p&gt;

&lt;h4&gt;
  
  
  When the spreadsheet is the right answer
&lt;/h4&gt;

&lt;p&gt;If one person maintains it, the numbers still match reality and nobody is waiting on it, leave it alone. Software should remove work, and a dashboard nobody opens is just a new thing to maintain.&lt;/p&gt;

&lt;p&gt;The same goes for the tool you already pay for. If your shop platform or accounts package can produce the report, I would rather connect the two than build a screen that duplicates it.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;One person owns the file, and it is part of their job.&lt;/li&gt;
&lt;li&gt;The numbers still match the bank and the warehouse.&lt;/li&gt;
&lt;li&gt;Nobody waits on it to answer a question.&lt;/li&gt;
&lt;li&gt;A tool you already pay for can produce the same report.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;A screen that duplicates a report your platform already produces is a bill without a benefit, and saying so is part of the first call.&lt;/p&gt;

&lt;h4&gt;
  
  
  How do I start, so the cost stays low?
&lt;/h4&gt;

&lt;p&gt;I write down the six questions the owner asks every week, and build the screen that answers those. Nothing else. Small jobs start at $49, so a single report is a cheap way to find out whether this is worth doing.&lt;/p&gt;

&lt;p&gt;After that first screen, the next ones are usually quick, because the data is already in one place and already trusted. That is the real saving: the second screen is not a second project.&lt;/p&gt;

&lt;p&gt;The reason to start with the questions rather than with the data is that it fixes the scope. "Everything about the business" is not a screen anybody opens. "What sold yesterday, what is late, and what is owed" is.&lt;/p&gt;

&lt;h4&gt;
  
  
  Does a dashboard need AI?
&lt;/h4&gt;

&lt;p&gt;Usually no. A dashboard is arithmetic and access control. AI earns its place on a separate job, like recommending a price or summarising what changed this week.&lt;/p&gt;

&lt;p&gt;That distinction matters when you are getting quotes. If a proposal puts a model in front of a sum, ask what the model decides that arithmetic could not. Often the answer is nothing, and you are paying for a word.&lt;/p&gt;

&lt;h4&gt;
  
  
  What does it cost to run afterwards?
&lt;/h4&gt;

&lt;p&gt;Very little for a small business: hosting and a database, often a few dollars a month at first. The real question is who fixes it when a feed stops sending, which is what a support plan covers.&lt;/p&gt;

&lt;p&gt;I quote one fixed price after a free call and a written plan, so you know the number before I start. After launch I stay on as your engineer on a monthly plan from $149 a month, for as long as it is useful. The code and the accounts are in your name, so the plan is a choice rather than a lock-in.&lt;/p&gt;

&lt;p&gt;Takeaways:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Replace the file when it stops being one person's job.&lt;/li&gt;
&lt;li&gt;Start with the questions the owner asks every week.&lt;/li&gt;
&lt;li&gt;Every figure on the screen should trace back to the rows behind it.&lt;/li&gt;
&lt;li&gt;If an existing tool can produce the report, connect it instead.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Q: Can you move my spreadsheet into a database?&lt;br&gt;
A: Yes, and that is usually the first step. The old file keeps working while the new one is checked against it, so nobody has to trust a number they cannot verify.&lt;/p&gt;

&lt;p&gt;Q: Will my team actually use it?&lt;br&gt;
A: They use it when it is quicker than the alternative and works on the phone in their pocket. That is why I build around the process they already follow instead of asking them to change it.&lt;/p&gt;

&lt;p&gt;Q: Can it show my ecommerce numbers from more than one shop?&lt;br&gt;
A: Yes, and that is the most common reason people come to me. One screen for every shop, with the numbers that matter to you rather than the ones a platform chose to show.&lt;/p&gt;

&lt;p&gt;Sources:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;EuSpRIG, spreadsheet risk research: &lt;a href="https://eusprig.org/" rel="noopener noreferrer"&gt;https://eusprig.org/&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;PostgreSQL documentation: &lt;a href="https://www.postgresql.org/docs/" rel="noopener noreferrer"&gt;https://www.postgresql.org/docs/&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;Supabase row level security: &lt;a href="https://supabase.com/docs/guides/database/postgres/row-level-security" rel="noopener noreferrer"&gt;https://supabase.com/docs/guides/database/postgres/row-level-security&lt;/a&gt;
&lt;/li&gt;
&lt;/ul&gt;




&lt;p&gt;The full guide, with its sources, is at &lt;a href="https://najam.dev/guides/dashboard-or-spreadsheet/" rel="noopener noreferrer"&gt;https://najam.dev/guides/dashboard-or-spreadsheet/&lt;/a&gt;. If you want the short version of how I work: one engineer, one fixed price agreed in writing before anything starts, and the code and the accounts stay in your name. More at &lt;a href="https://najam.dev" rel="noopener noreferrer"&gt;https://najam.dev&lt;/a&gt;&lt;/p&gt;

</description>
      <category>productivity</category>
      <category>webdev</category>
      <category>database</category>
      <category>startup</category>
    </item>
    <item>
      <title>Should I hire an agency, a freelancer, or an agentic developer?</title>
      <dc:creator>Muhammad Najam Ul Hassan</dc:creator>
      <pubDate>Sun, 08 Nov 2026 19:14:01 +0000</pubDate>
      <link>https://dev.to/itsnajam/should-i-hire-an-agency-a-freelancer-or-an-agentic-developer-5429</link>
      <guid>https://dev.to/itsnajam/should-i-hire-an-agency-a-freelancer-or-an-agentic-developer-5429</guid>
      <description>&lt;p&gt;I build apps, websites and automation for small businesses and founders, and I am one of the four options in this comparison, so I wrote it with my own column kept honest.&lt;/p&gt;

&lt;p&gt;Four ways to get software built, compared by what they sell you rather than by what they call themselves. The honest version, including the jobs where I am the wrong answer.&lt;/p&gt;

&lt;p&gt;Short answer:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;An agency sells a process and people to point at. A freelancer sells their own hours. A no-code builder sells speed inside a tool's limits. An agentic developer sells what a senior engineer always sold, with faster drafting.&lt;/li&gt;
&lt;li&gt;The price gap is mostly the cost of the people who are not writing code, not a difference in quality.&lt;/li&gt;
&lt;li&gt;Agents made the typing cheaper. They did not make the decisions cheaper, and the decisions are most of what you pay for.&lt;/li&gt;
&lt;li&gt;The published research on AI coding speed genuinely disagrees with itself: one controlled task finished 55.8% faster with an assistant, while experienced developers working inside repositories they already knew took 19% longer.&lt;/li&gt;
&lt;li&gt;Ask the same six questions of every quote. Who owns the code and the accounts afterwards is the one most buyers forget to ask.&lt;/li&gt;
&lt;/ul&gt;

&lt;h4&gt;
  
  
  Which one fits which situation?
&lt;/h4&gt;

&lt;p&gt;Each option is selling a different thing, and the price gap follows that. An agency sells a process and a set of people your procurement team can point at. A freelancer sells their own hours and their own judgement. A no-code builder sells speed inside the limits its tooling allows. An agentic senior developer sells what a senior engineer always sold, with the drafting done faster and the checking done the same careful way.&lt;br&gt;
So the choice follows what the job actually needs: a process and paperwork a larger organisation can sign, one pair of hands answering quickly, the fastest route to something working without code, or one person accountable from the plan to the store listing and the month after launch.&lt;br&gt;
If your real question is whether to hire anyone at all versus building it in a builder, that comparison has its own page: &lt;a href="https://najam.dev/guides/app-builder-or-developer/" rel="noopener noreferrer"&gt;app builder or developer&lt;/a&gt;. This one is about who to hire once you have decided to hire.&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;The situation&lt;/th&gt;
&lt;th&gt;What usually fits&lt;/th&gt;
&lt;th&gt;Why&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;A programme with several teams, audits and reporting&lt;/td&gt;
&lt;td&gt;Agency&lt;/td&gt;
&lt;td&gt;The paperwork is part of the product, and someone has to own it&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;A known fix inside a system somebody else built&lt;/td&gt;
&lt;td&gt;Freelancer, or a takeover&lt;/td&gt;
&lt;td&gt;Small surface, one skill set, no team ramp-up to pay for&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;An internal workflow four people use&lt;/td&gt;
&lt;td&gt;No-code builder&lt;/td&gt;
&lt;td&gt;Quicker and cheaper than any hire when the standard patterns already fit&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;A product with logins, payments and a store listing&lt;/td&gt;
&lt;td&gt;Agentic senior developer&lt;/td&gt;
&lt;td&gt;One person accountable end to end, at one fixed price&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;A first version to find out whether anyone pays&lt;/td&gt;
&lt;td&gt;Me or a builder, depending on the idea&lt;/td&gt;
&lt;td&gt;Learning beats architecture until someone opens a wallet&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;h4&gt;
  
  
  The four options side by side
&lt;/h4&gt;

&lt;p&gt;Fair to all four, because none of them is a trick. An agency that runs well is worth what it charges on the right job, and a good freelancer is the best value in this market on a narrow one. What the columns describe is where the risk sits and who carries it, not a ranking.&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;The question&lt;/th&gt;
&lt;th&gt;Traditional agency&lt;/th&gt;
&lt;th&gt;Solo freelancer&lt;/th&gt;
&lt;th&gt;No-code builder&lt;/th&gt;
&lt;th&gt;Agentic senior developer&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Cost to start&lt;/td&gt;
&lt;td&gt;Highest: an account layer sits on top of the hours&lt;/td&gt;
&lt;td&gt;Lower on the same scope, because the layer is one person&lt;/td&gt;
&lt;td&gt;Lowest in the first months, then subscriptions and add-ons&lt;/td&gt;
&lt;td&gt;One fixed price agreed in writing, from $2,999 for an app&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Speed to a first clickable version&lt;/td&gt;
&lt;td&gt;Slowest: discovery, scoping and ramp-up come first&lt;/td&gt;
&lt;td&gt;Fast when the scope is small and they are free now&lt;/td&gt;
&lt;td&gt;Fastest for the shapes the tool knows&lt;/td&gt;
&lt;td&gt;Fast first draft, then the checking takes the time it always took&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Who writes the plan&lt;/td&gt;
&lt;td&gt;A manager and an architect, sometimes billed separately&lt;/td&gt;
&lt;td&gt;The person doing the work&lt;/td&gt;
&lt;td&gt;You, inside the tool's assumptions&lt;/td&gt;
&lt;td&gt;Me, in writing, before any agent runs&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Who checks the code&lt;/td&gt;
&lt;td&gt;Another engineer on the same team&lt;/td&gt;
&lt;td&gt;Nobody, unless you hire one&lt;/td&gt;
&lt;td&gt;The platform, for the parts it allows&lt;/td&gt;
&lt;td&gt;Me, line by line, with tests on the flows that cost money&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Who owns the code and the accounts&lt;/td&gt;
&lt;td&gt;Depends on the contract: work-for-hire is not automatic&lt;/td&gt;
&lt;td&gt;You, if the contract says so, so ask before signing&lt;/td&gt;
&lt;td&gt;The platform, until you can export and often after&lt;/td&gt;
&lt;td&gt;You, from the first commit, in your repository and your store accounts&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;What happens when someone leaves&lt;/td&gt;
&lt;td&gt;A handover inside the company; the name stays on the door&lt;/td&gt;
&lt;td&gt;The knowledge leaves with the person&lt;/td&gt;
&lt;td&gt;The subscription carries on and nobody knows why it was built that way&lt;/td&gt;
&lt;td&gt;Written plan and handover notes; the monthly plan is optional, not a lock-in&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Best for&lt;/td&gt;
&lt;td&gt;Multi-team programmes, audits, long maintenance contracts&lt;/td&gt;
&lt;td&gt;A defined piece of work in an existing system&lt;/td&gt;
&lt;td&gt;Simple internal tools and quick landing pages&lt;/td&gt;
&lt;td&gt;A whole small product: plan, build, store submission, support after&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Worst for&lt;/td&gt;
&lt;td&gt;A small fixed job where you would pay for the overhead&lt;/td&gt;
&lt;td&gt;Anything needing several skills at once or cover while someone is ill&lt;/td&gt;
&lt;td&gt;Custom logic, real data rules, owning your own product&lt;/td&gt;
&lt;td&gt;A programme that needs five or more engineers on it&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;h4&gt;
  
  
  How much faster is agentic development really?
&lt;/h4&gt;

&lt;p&gt;Faster on some work, and the published evidence is honest about how much and how little. In a controlled experiment run by GitHub and Microsoft Research, developers with a coding assistant completed a self-contained task 55.8% faster than the control group. In METR's 2025 study of experienced open-source developers working on mature repositories they already knew well, being allowed to use AI tools made tasks take 19% longer, while the same developers finished believing they had been about 20% faster. Both of those are real, and they are the two ends of the range rather than a average of it.&lt;br&gt;
The difference is what the task was. The fast result came from a small, well-specified job that the developers had not seen before. The slow one came from experts inside a codebase they already carried in their heads, where describing the change to a tool cost more than writing it. My work sits between those two, nearer the fast end when the job is new screens, forms, list views, report queries, tests and plumbing, and nearer the slow end when it is one careful change to something only I understand.&lt;br&gt;
What I take from it is the same line I put on the &lt;a href="https://najam.dev/services/agentic-software-development/" rel="noopener noreferrer"&gt;agentic software development&lt;/a&gt; page: the drafting got much cheaper and the parts that were never about typing did not. The first call, the plan, the data rules, the privacy answers Apple and Google ask for, and the decision about what not to build still take what they take.&lt;br&gt;
Where the speed is real for you is in the first clickable version and in every revision after it. A change you ask for on Tuesday is on your phone on Wednesday, and that is the part a fixed price absorbs and an hourly invoice does not.&lt;/p&gt;

&lt;h4&gt;
  
  
  Where do agents save time and where do they not?
&lt;/h4&gt;

&lt;p&gt;The split is the same one I use on every build, and it is not a rule about which tool is cleverest. It is one question: how much of this job is typing, and how much of it is knowing your business.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Where the risk of being wrong is high, an agent drafts and I write or rewrite the part myself. That is the same conclusion as the checklist on the &lt;a href="https://najam.dev/guides/how-i-build-with-ai/" rel="noopener noreferrer"&gt;AI-assisted coding&lt;/a&gt; guide.&lt;/li&gt;
&lt;li&gt;The demo is not the difficult part any more, which is why so much work now arrives as a cleanup: see the &lt;a href="https://najam.dev/guides/vibe-coding-cleanup/" rel="noopener noreferrer"&gt;vibe coding cleanup&lt;/a&gt; guide for what that costs.&lt;/li&gt;
&lt;/ul&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Saves real hours&lt;/th&gt;
&lt;th&gt;Saves nothing&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Screens, forms, filters and list views&lt;/td&gt;
&lt;td&gt;Deciding what the product should do&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Test scaffolding and the boring coverage&lt;/td&gt;
&lt;td&gt;A data model you only get to design once&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Migrations and repetitive plumbing with a clear pattern&lt;/td&gt;
&lt;td&gt;Permissions, payments and the failure paths&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;First drafts of copy variants and reports&lt;/td&gt;
&lt;td&gt;Store submissions and the privacy forms&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Reading an unfamiliar library's API so I do not have to&lt;/td&gt;
&lt;td&gt;Cleaning up data someone else typed in by hand&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Revisions you ask for week after week&lt;/td&gt;
&lt;td&gt;Anything that takes more care to explain than to write&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;h4&gt;
  
  
  What does agentic software development cost?
&lt;/h4&gt;

&lt;p&gt;There is no premium for the agentic label and no discount for it, because you are paying for the thing you asked for. My published starting points are on &lt;a href="https://najam.dev/services/" rel="noopener noreferrer"&gt;Services&lt;/a&gt;: an app from $2,999, a web app or dashboard from $799, an automation from $499, a landing page from $299. Small jobs start at $49. Support after launch is from $149 a month.&lt;br&gt;
Why an agency quote for the same scope comes in higher, in plain terms: you are paying for a name, a manager, a designer, a QA person and the paperwork that comes with them, and on some jobs that is exactly what you need. On a small product the account layer is a large share of the bill, so the same scope costs less with one engineer and more the more seats sit around it. I am not going to quote you a market average for agency rates, because I do not have a source I would put my name on.&lt;br&gt;
What to hold every option to, including me: one fixed price, agreed in writing before the first line exists, with the date and the handover written in the same document.&lt;/p&gt;

&lt;h4&gt;
  
  
  How do you compare quotes from different kinds of supplier?
&lt;/h4&gt;

&lt;p&gt;Ask the same six questions in the same words to all of them, and write the answers down. They tell you more than the price line does, and &lt;a href="https://najam.dev/guides/what-an-app-costs/" rel="noopener noreferrer"&gt;what an app costs&lt;/a&gt; walks through the arithmetic behind each number.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Is the price fixed or hourly, and what is the thing that makes it change?&lt;/li&gt;
&lt;li&gt;Who writes the plan, and is it inside the price or billed as a separate phase?&lt;/li&gt;
&lt;li&gt;Who reads and tests the code before it ships, and what stops it if it is wrong?&lt;/li&gt;
&lt;li&gt;Who owns the repository, the store accounts, the server and the keys afterwards?&lt;/li&gt;
&lt;li&gt;What happens in month three when something breaks and the person who built it is busy?&lt;/li&gt;
&lt;li&gt;What is the handover, exactly, in writing?&lt;/li&gt;
&lt;/ul&gt;

&lt;h4&gt;
  
  
  When should you not hire me?
&lt;/h4&gt;

&lt;p&gt;When the work needs several teams at once, formal audits, or a supplier your procurement department can hold to a contract, an agency is the better answer. If the plan needs five or more engineers, a compliance function, or 24/7 cover with a phone number and an escalation path, hire the firm that provides those, because I do not and no tool changes that.&lt;br&gt;
When the job is a simple internal workflow that a handful of people use and nothing unusual is in the rules, a no-code builder is faster and cheaper than I am, and paying an engineer to rebuild what a template already does is a bad hire.&lt;br&gt;
When the work is one narrow job inside a system I have never seen, the freelancer who already knows that codebase will beat me on both price and time.&lt;br&gt;
And when what is actually missing is agreement inside your own company about what to build, software will not settle it. I build what the plan says, and I will not charge you for pretending to be a strategy department.&lt;/p&gt;

&lt;p&gt;Takeaways:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Choose by what the job needs from the person, not by the size of the shop.&lt;/li&gt;
&lt;li&gt;An agency's price contains the account layer, a solo price contains only the hours, a builder's price contains its limits.&lt;/li&gt;
&lt;li&gt;Agents made typing cheaper and left the decisions at their old price.&lt;/li&gt;
&lt;li&gt;The AI speed research is genuinely mixed: 55.8% faster on a self-contained task, 19% slower for experts in code they already knew.&lt;/li&gt;
&lt;li&gt;Own the repository and the accounts from the first commit, whoever builds it.&lt;/li&gt;
&lt;li&gt;Ask the same six questions of every quote; the differences show up in the answers, not the totals.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Q: Is an AI-assisted developer cheaper than an agency?&lt;br&gt;
A: On the same scope, usually yes, because there is no account layer sitting on top of the work. That is a difference in the shape of the business, not in quality. The gap closes when the process is what you are buying: several workstreams, audits, and cover while people are ill. My own prices do not change with how the code gets drafted, so an agentic build is not a premium and not a discount.&lt;/p&gt;

&lt;p&gt;Q: Can I hire an agency and an agentic developer together?&lt;br&gt;
A: Yes, and it is a common shape. The agency owns the platform and its process, and one person builds and ships a defined piece inside it. Fix two things in writing before starting: who signs off the merge into the shared branch, and who answers when something breaks outside office hours. Everything else follows from those.&lt;/p&gt;

&lt;p&gt;Q: Do I still need a person if AI can write the code?&lt;br&gt;
A: You need someone who owns the outcome, and that is what you have always been buying. A model can write a refund flow; it cannot decide what your business should do when a refund is wrong, whose fault it is when a payment fails twice, or whether this screen should exist at all. In all four options the accountable human is the product.&lt;/p&gt;

&lt;p&gt;Q: Who is responsible if agentic development gets something wrong?&lt;br&gt;
A: Me, and only me. It is one contract, one name and one fixed price, so there is nobody to hide behind when a screen misbehaves. The terms do not change because part of the work was drafted by an agent, and you do not have to take my word for any of it: the repository starts in your name, and the handover says which parts came from an agent and which I wrote.&lt;/p&gt;

&lt;p&gt;Q: Does AI-written code hold up in production?&lt;br&gt;
A: Only when someone reads it before it ships. Whatever the tooling, the failures arrive in the same handful of places, and none of them is a syntax problem: who is allowed to see this record, what happens when a charge fails twice, what the app shows when the network does not answer. That is a checklist rather than a model choice, and mine is written out on the &lt;a href="https://najam.dev/guides/how-i-build-with-ai/" rel="noopener noreferrer"&gt;AI-assisted coding&lt;/a&gt; guide.&lt;/p&gt;

&lt;p&gt;Sources:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;METR: measuring the impact of early-2025 AI on experienced open-source developer productivity: &lt;a href="https://metr.org/blog/2025-07-10-early-2025-ai-experienced-os-dev-study/" rel="noopener noreferrer"&gt;https://metr.org/blog/2025-07-10-early-2025-ai-experienced-os-dev-study/&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;GitHub research: quantifying GitHub Copilot's impact on developer productivity and happiness: &lt;a href="https://github.blog/news-insights/research/research-quantifying-github-copilots-impact-on-developer-productivity-and-happiness/" rel="noopener noreferrer"&gt;https://github.blog/news-insights/research/research-quantifying-github-copilots-impact-on-developer-productivity-and-happiness/&lt;/a&gt;
&lt;/li&gt;
&lt;/ul&gt;




&lt;p&gt;Originally published at &lt;a href="https://najam.dev/guides/agentic-developer-vs-agency/" rel="noopener noreferrer"&gt;https://najam.dev/guides/agentic-developer-vs-agency/&lt;/a&gt;. If you want the short version of how I work: one engineer, one fixed price agreed in writing before anything starts, and the code and the accounts stay in your name. More at &lt;a href="https://najam.dev" rel="noopener noreferrer"&gt;https://najam.dev&lt;/a&gt;&lt;/p&gt;

</description>
      <category>ai</category>
      <category>career</category>
      <category>webdev</category>
      <category>productivity</category>
    </item>
    <item>
      <title>How to hire an n8n developer without buying a mess</title>
      <dc:creator>Muhammad Najam Ul Hassan</dc:creator>
      <pubDate>Mon, 02 Nov 2026 10:51:44 +0000</pubDate>
      <link>https://dev.to/itsnajam/how-to-hire-an-n8n-developer-without-buying-a-mess-mpk</link>
      <guid>https://dev.to/itsnajam/how-to-hire-an-n8n-developer-without-buying-a-mess-mpk</guid>
      <description>&lt;p&gt;I build apps, websites and automation for small businesses and founders, and n8n is a tool inside that work rather than the headline. This is the same guide that lives on my site.&lt;/p&gt;

&lt;p&gt;n8n is easy to start and hard to leave running. Anyone can drag three nodes onto a canvas and watch them fire once. What you are hiring for is what happens on the day a step fails.&lt;/p&gt;

&lt;p&gt;Short answer:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;An n8n developer builds and maintains automations that connect the tools you already use. The skill is not the canvas, it is the failure handling.&lt;/li&gt;
&lt;li&gt;Ask three things before anything else: where the workflow runs, who owns the account, and what happens when a step fails.&lt;/li&gt;
&lt;li&gt;A good build has an error path, a log, and a person who gets told when it breaks.&lt;/li&gt;
&lt;li&gt;You pay once for the build. The n8n plan or server, any model calls, and the other tools' own plans are separate monthly costs, and most quotes leave them out.&lt;/li&gt;
&lt;li&gt;If you cannot export it, you do not own it.&lt;/li&gt;
&lt;/ul&gt;

&lt;h4&gt;
  
  
  What does an n8n developer do?
&lt;/h4&gt;

&lt;p&gt;An n8n developer builds automations: workflows that move data between the tools a business already uses, add logic where those tools do not, and keep running without someone clicking through them.&lt;/p&gt;

&lt;p&gt;Most of the work I do in n8n is one of these:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Sorting enquiries and routing them to the right person.&lt;/li&gt;
&lt;li&gt;Reading documents and pulling out the fields that matter.&lt;/li&gt;
&lt;li&gt;Syncing a shop with a warehouse or an accounts package.&lt;/li&gt;
&lt;li&gt;Building a daily report from several systems.&lt;/li&gt;
&lt;li&gt;Putting an AI step behind a human approval.&lt;/li&gt;
&lt;/ul&gt;

&lt;h4&gt;
  
  
  The ten questions to ask before hiring
&lt;/h4&gt;

&lt;p&gt;These tell you more than a portfolio, which only ever shows the happy path.&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Where will the workflow run: n8n's cloud or a server you control?&lt;/li&gt;
&lt;li&gt;Who owns the n8n account and the workflow files?&lt;/li&gt;
&lt;li&gt;What happens when a step fails: retries, an error workflow, and who gets told?&lt;/li&gt;
&lt;li&gt;What happens if the same record arrives twice?&lt;/li&gt;
&lt;li&gt;Where do the credentials live, and who can read them?&lt;/li&gt;
&lt;li&gt;How is the workflow tested before it touches real data?&lt;/li&gt;
&lt;li&gt;What will it cost to run at my volume, including the n8n plan and any model calls?&lt;/li&gt;
&lt;li&gt;What breaks first when the volume grows, and what does fixing it involve?&lt;/li&gt;
&lt;li&gt;Can I export everything if I stop working with you?&lt;/li&gt;
&lt;li&gt;Who fixes it when it breaks after launch?&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;The answers that matter are specific. "I handle errors" is not one. "Each workflow has an error trigger that logs the failed execution and messages me, and the retry is idempotent" is.&lt;/p&gt;

&lt;p&gt;Question 4 is the one most buyers skip and most cheap builds fail. A flaky API times out, the workflow retries, and the record arrives twice. Without a check for that you get two invoices, or two rows in a report nobody reconciles.&lt;/p&gt;

&lt;h4&gt;
  
  
  What does an n8n build cost?
&lt;/h4&gt;

&lt;p&gt;I quote one fixed price after a free call, the same as any other build: a written plan of the workflows and the failure cases, then a price. Small jobs start at $49, like a single workflow or a fix.&lt;/p&gt;

&lt;p&gt;The build is one bill. The running costs are separate, and they are the part most quotes leave out.&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Running cost&lt;/th&gt;
&lt;th&gt;What it covers&lt;/th&gt;
&lt;th&gt;How it scales&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;n8n plan or server&lt;/td&gt;
&lt;td&gt;The tool itself: a cloud plan, or a server you pay for&lt;/td&gt;
&lt;td&gt;With executions on cloud, with the server if self-hosted&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;AI model calls&lt;/td&gt;
&lt;td&gt;Any step that asks a model to read, sort or draft&lt;/td&gt;
&lt;td&gt;With the number and size of calls&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;The tools being connected&lt;/td&gt;
&lt;td&gt;The other systems' own plans&lt;/td&gt;
&lt;td&gt;With their own limits, not n8n's&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Maintenance&lt;/td&gt;
&lt;td&gt;Someone to watch it, update it and fix what breaks&lt;/td&gt;
&lt;td&gt;Usually a monthly support arrangement&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;Ask for that table filled in with your volumes.&lt;/p&gt;

&lt;p&gt;On timing: a single workflow is often days. A set of workflows with error handling, testing and a handover is usually weeks. The plan fixes the scope before the price, so the date and the price move together.&lt;/p&gt;

&lt;h4&gt;
  
  
  n8n cloud or self-hosted?
&lt;/h4&gt;

&lt;p&gt;Both are n8n. The difference is who looks after the machine.&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;What matters&lt;/th&gt;
&lt;th&gt;n8n cloud&lt;/th&gt;
&lt;th&gt;Self-hosted&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Who runs it&lt;/td&gt;
&lt;td&gt;n8n&lt;/td&gt;
&lt;td&gt;You, or whoever you pay to run it&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Monthly cost&lt;/td&gt;
&lt;td&gt;A plan that follows executions&lt;/td&gt;
&lt;td&gt;Server and database costs, usually fixed&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Data location&lt;/td&gt;
&lt;td&gt;n8n's infrastructure&lt;/td&gt;
&lt;td&gt;Your own server&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Upgrades&lt;/td&gt;
&lt;td&gt;Handled for you&lt;/td&gt;
&lt;td&gt;Someone has to do them&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Fits when&lt;/td&gt;
&lt;td&gt;Most small businesses&lt;/td&gt;
&lt;td&gt;High volume, data that must stay put, or existing infrastructure&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;Self-hosting is not automatically cheaper once you count the person who does the upgrades. It fits high volume, data that must stay put, or existing infrastructure.&lt;/p&gt;

&lt;h4&gt;
  
  
  What a bad n8n build looks like
&lt;/h4&gt;

&lt;p&gt;The failures repeat, which makes them easy to spot once you know them.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;No error handling, so a failed step disappears and the work it was doing never happens.&lt;/li&gt;
&lt;li&gt;One enormous workflow with no notes, which nobody else can safely change.&lt;/li&gt;
&lt;li&gt;Credentials in a shared document or a message thread.&lt;/li&gt;
&lt;li&gt;No retry logic, so a flaky API creates duplicates.&lt;/li&gt;
&lt;li&gt;An AI step that sends customer messages without a person approving them.&lt;/li&gt;
&lt;li&gt;No log of what came in and what went out, so a wrong result cannot be traced.&lt;/li&gt;
&lt;li&gt;Built in the developer's personal account, with no handover.&lt;/li&gt;
&lt;li&gt;No export, so leaving means starting again.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The quiet ones are the expensive ones. A workflow that stops loudly gets fixed the same day. One that drops one record in fifty keeps running for months.&lt;/p&gt;

&lt;h4&gt;
  
  
  How I work on an n8n job
&lt;/h4&gt;

&lt;p&gt;If you want me to build, fix or take over your workflows, the &lt;a href="https://najam.dev/services/n8n-development/" rel="noopener noreferrer"&gt;n8n development page&lt;/a&gt; has the details and prices. If Zapier or Make is the better fit for what you need, I will say so, and the &lt;a href="https://najam.dev/guides/n8n-vs-make-vs-zapier/" rel="noopener noreferrer"&gt;comparison guide&lt;/a&gt; explains why.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;The workflows and the failure cases are written down before anything is built.&lt;/li&gt;
&lt;li&gt;It is built in an n8n account in your name, so you keep it.&lt;/li&gt;
&lt;li&gt;Every workflow gets an error path, a log and an alert to a person.&lt;/li&gt;
&lt;li&gt;I test it with your real sample data, then with the cases that usually break: empty fields, duplicates, timeouts, a model returning nonsense.&lt;/li&gt;
&lt;li&gt;You get a written handover, and a support plan if you want someone on call.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;After launch I stay on as your engineer on a monthly plan from $149 a month. The handover is written so it works without me.&lt;/p&gt;

&lt;h4&gt;
  
  
  Do you need a developer, or can you do it yourself?
&lt;/h4&gt;

&lt;p&gt;n8n rewards people who can think in steps and conditions. If the workflow is simple, the volume is low and you have the time, the tutorials are good and you can get a long way.&lt;/p&gt;

&lt;p&gt;Hire help when the workflow touches money, customer data or a deadline. Those are the places where a quiet failure costs more than the build.&lt;/p&gt;

&lt;p&gt;Takeaways:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Ask where it runs, who owns it and what happens when a step fails.&lt;/li&gt;
&lt;li&gt;A good build has an error path, a log and a person who gets told.&lt;/li&gt;
&lt;li&gt;If you cannot export it, you do not own it.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Q: What does it cost to hire an n8n developer?&lt;br&gt;
A: One fixed price for the work, quoted after a free call and a written plan. Small jobs start at $49. The n8n plan, the server and any model calls are separate running costs, worked out from published prices and your volume before the build.&lt;/p&gt;

&lt;p&gt;Q: Can you fix an n8n workflow someone else built?&lt;br&gt;
A: Yes. I read it first, find the places where it fails quietly, and tell you whether tidying it or rebuilding it costs less. That verdict is in writing, whether or not you hire me for the rest.&lt;/p&gt;

&lt;p&gt;Q: Is n8n better than Zapier or Make?&lt;br&gt;
A: It depends on the job. n8n is strongest when volume is high, you need a real code step, or you want to host it yourself. Zapier and Make are often better for simple flows and for people who want to edit them without help.&lt;/p&gt;

&lt;p&gt;Sources:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;n8n documentation: &lt;a href="https://docs.n8n.io/" rel="noopener noreferrer"&gt;https://docs.n8n.io/&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;n8n error handling: &lt;a href="https://docs.n8n.io/flow-logic/error-handling/" rel="noopener noreferrer"&gt;https://docs.n8n.io/flow-logic/error-handling/&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;n8n self-hosting: &lt;a href="https://docs.n8n.io/hosting/" rel="noopener noreferrer"&gt;https://docs.n8n.io/hosting/&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;n8n pricing: &lt;a href="https://n8n.io/pricing/" rel="noopener noreferrer"&gt;https://n8n.io/pricing/&lt;/a&gt;
&lt;/li&gt;
&lt;/ul&gt;




&lt;p&gt;The full guide, with its sources, is at &lt;a href="https://najam.dev/guides/hire-an-n8n-developer/" rel="noopener noreferrer"&gt;https://najam.dev/guides/hire-an-n8n-developer/&lt;/a&gt;. If you want the short version of how I work: one engineer, one fixed price agreed in writing before anything starts, and the code and the accounts stay in your name. More at &lt;a href="https://najam.dev" rel="noopener noreferrer"&gt;https://najam.dev&lt;/a&gt;&lt;/p&gt;

</description>
      <category>automation</category>
      <category>hiring</category>
      <category>freelance</category>
      <category>n8n</category>
    </item>
    <item>
      <title>What it actually costs to build an app, and how to compare two quotes</title>
      <dc:creator>Muhammad Najam Ul Hassan</dc:creator>
      <pubDate>Sat, 31 Oct 2026 09:00:47 +0000</pubDate>
      <link>https://dev.to/itsnajam/what-it-actually-costs-to-build-an-app-and-how-to-compare-two-quotes-3bfk</link>
      <guid>https://dev.to/itsnajam/what-it-actually-costs-to-build-an-app-and-how-to-compare-two-quotes-3bfk</guid>
      <description>&lt;p&gt;Nobody can price an app from one sentence. Here is what the price is actually made of, and how to get a quote you can compare against another one.&lt;/p&gt;

&lt;p&gt;Short answer:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;The number comes from screens, sign-in, payments, admin screens and integrations, not from the idea.&lt;/li&gt;
&lt;li&gt;Small jobs start at $49. A full product is quoted as one fixed price after a free call.&lt;/li&gt;
&lt;li&gt;Store accounts, hosting and any AI bill are running costs, separate from the build.&lt;/li&gt;
&lt;li&gt;The cheapest quote usually leaves something out that you pay to add back later.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Why do two developers quote different numbers?
&lt;/h2&gt;

&lt;p&gt;Because they are not quoting the same thing. One is quoting the app you described, and the other is quoting the app you will want in six months: the admin screen, the refunds, the offline mode, the second language.&lt;br&gt;
There is no honest way to compare two quotes until you can see what each one includes. That is why I write the plan down before the price, so you can put my list next to anyone else's.&lt;/p&gt;

&lt;h2&gt;
  
  
  What actually moves the price?
&lt;/h2&gt;

&lt;p&gt;These are the things I count when I quote. Each one is a real piece of work, and each one is also something you can choose to leave out of the first version.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;How many screens there are, and how different they are from each other.&lt;/li&gt;
&lt;li&gt;Whether people sign in, and whether there are different kinds of people with different views.&lt;/li&gt;
&lt;li&gt;Whether money moves: cards, subscriptions, refunds, payouts, receipts.&lt;/li&gt;
&lt;li&gt;How much admin sits behind it. Someone has to add the products, approve the jobs and fix the mistakes.&lt;/li&gt;
&lt;li&gt;What it has to talk to: your shop platform, your accounts package, a spreadsheet, a supplier feed.&lt;/li&gt;
&lt;li&gt;Content. Writing, photography and prices take somebody's time, usually yours.&lt;/li&gt;
&lt;li&gt;The stores. Apple and Google both have accounts, rules and a submission process.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Does AI make an app cheaper?
&lt;/h2&gt;

&lt;p&gt;It makes the typing faster, not the deciding cheaper. Screens and plumbing take less time. The plan, your data, payments, admin screens and store rules are the same work.&lt;br&gt;
I wrote a separate guide on what an app built with AI costs, including the model bill that arrives after launch.&lt;/p&gt;

&lt;h2&gt;
  
  
  What costs do people forget?
&lt;/h2&gt;

&lt;p&gt;The build is the number everyone asks about, and it is not the only one. These keep running after launch.&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Cost&lt;/th&gt;
&lt;th&gt;When you pay it&lt;/th&gt;
&lt;th&gt;Who it goes to&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Apple developer account&lt;/td&gt;
&lt;td&gt;A yearly fee, before the app can go live&lt;/td&gt;
&lt;td&gt;Apple&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Google Play developer account&lt;/td&gt;
&lt;td&gt;A one-off registration fee&lt;/td&gt;
&lt;td&gt;Google&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Domain name&lt;/td&gt;
&lt;td&gt;Yearly&lt;/td&gt;
&lt;td&gt;Your registrar&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Hosting and database&lt;/td&gt;
&lt;td&gt;Monthly, usually small at first&lt;/td&gt;
&lt;td&gt;The host or platform&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Payment processing&lt;/td&gt;
&lt;td&gt;A percentage of each payment&lt;/td&gt;
&lt;td&gt;The payment provider&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;AI model calls, if the product uses them&lt;/td&gt;
&lt;td&gt;Monthly, based on volume&lt;/td&gt;
&lt;td&gt;The model provider&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Looking after it&lt;/td&gt;
&lt;td&gt;Monthly, if you want an engineer on call&lt;/td&gt;
&lt;td&gt;Me, on a support plan&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;h2&gt;
  
  
  How much does it cost to hire an app developer?
&lt;/h2&gt;

&lt;p&gt;There is no single number, which is why quotes for the same idea range from a few hundred dollars to tens of thousands. The useful question is not the hourly rate, it is what the quote includes and who carries the risk when the estimate is wrong.&lt;br&gt;
Hourly works when the work is genuinely unknown, like a rescue where nobody knows what is broken until the code is read. It punishes you when the scope is clear, because every change reopens the bill. A fixed price works when the plan is written down, because the number stays still unless the work changes.&lt;br&gt;
Offshore teams are often cheaper per hour and cost more in the end when the time zone, the language and the handover add management you did not budget for. Local developers cost more per hour and can be faster to reach. Either way, what matters is a written plan and one person accountable for the result.&lt;br&gt;
My fixed price includes the plan, the build, testing of the main flows, the store submission when there is an app, and the fix-it promise if what I deliver does not do what the plan says. Small jobs start at $49. The Apple and Google developer accounts and any hosting or AI bills are separate running costs you own.&lt;/p&gt;

&lt;h2&gt;
  
  
  How I quote
&lt;/h2&gt;

&lt;p&gt;A free first call, then a written plan that says what I will build and what it will not do, then one fixed price. The price does not move unless the work does, and if what I deliver does not do what the plan says, I fix it at no extra cost.&lt;br&gt;
Small jobs start at $49: a fix, a screen, a small automation. If the honest answer is that you do not need software at all, I will say that on the call instead of quoting you.&lt;/p&gt;

&lt;h2&gt;
  
  
  How to get a quote you can compare
&lt;/h2&gt;

&lt;p&gt;Send the same short brief to everyone you ask. The more specific it is, the more the quotes mean.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Who uses it, and what each kind of user needs to do.&lt;/li&gt;
&lt;li&gt;The screens you can already picture, even roughly.&lt;/li&gt;
&lt;li&gt;Whether money moves, and who receives it.&lt;/li&gt;
&lt;li&gt;Anything it has to connect to that already exists.&lt;/li&gt;
&lt;li&gt;Your deadline, and what happens if it slips.&lt;/li&gt;
&lt;li&gt;Who looks after it after launch.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Takeaways:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Price the screens, the sign-in, the money and the admin, not the idea.&lt;/li&gt;
&lt;li&gt;Compare what is included before you compare numbers.&lt;/li&gt;
&lt;li&gt;Budget for running costs from the day it goes live.&lt;/li&gt;
&lt;li&gt;Get the plan in writing, so the price means something.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Q: Can you give me a price over email?&lt;br&gt;
A: I can give you a small-job price, because those start at $49. For anything bigger I need to understand it first, and I would rather be accurate than fast. The first call is free and usually settles it.&lt;/p&gt;

&lt;p&gt;Q: Do you charge by the hour?&lt;br&gt;
A: No. You get one fixed price for the work in the plan. Hourly billing puts the risk of my mistakes on you, and that is the wrong way round.&lt;/p&gt;

&lt;p&gt;Q: Is it cheaper to start with a website?&lt;br&gt;
A: Often yes. A website can be found on Google and does not need two store accounts, so for one shop or one trade it is usually the sensible first step. I will tell you if that is the case for you.&lt;/p&gt;

&lt;p&gt;Q: What if the price changes halfway through?&lt;br&gt;
A: Only if the work changes. If you add something that was not in the plan, I will tell you what it costs before I build it, and you decide.&lt;/p&gt;

&lt;p&gt;Q: Why do agencies quote more than you do?&lt;br&gt;
A: An agency has more people to pay and more coordination, so the same work carries more overhead. That is not a comment on their quality, it is a different shape of business. With me you get one person who does the work and answers you directly.&lt;/p&gt;

&lt;p&gt;Sources:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Apple Developer Program: &lt;a href="https://developer.apple.com/programs/" rel="noopener noreferrer"&gt;https://developer.apple.com/programs/&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;Google Play Console registration: &lt;a href="https://support.google.com/googleplay/android-developer/answer/6112435" rel="noopener noreferrer"&gt;https://support.google.com/googleplay/android-developer/answer/6112435&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;Stripe pricing: &lt;a href="https://stripe.com/pricing" rel="noopener noreferrer"&gt;https://stripe.com/pricing&lt;/a&gt;
&lt;/li&gt;
&lt;/ul&gt;




&lt;p&gt;This is a republished version of a guide from my own site: &lt;a href="https://najam.dev/guides/what-an-app-costs/" rel="noopener noreferrer"&gt;https://najam.dev/guides/what-an-app-costs/&lt;/a&gt;. If you want a straight answer about your own build, the contact details are on &lt;a href="https://najam.dev" rel="noopener noreferrer"&gt;https://najam.dev&lt;/a&gt;.&lt;/p&gt;

</description>
      <category>startup</category>
      <category>beginners</category>
      <category>webdev</category>
    </item>
    <item>
      <title>n8n vs Make vs Zapier: pick by what you are actually automating</title>
      <dc:creator>Muhammad Najam Ul Hassan</dc:creator>
      <pubDate>Sat, 31 Oct 2026 03:18:55 +0000</pubDate>
      <link>https://dev.to/itsnajam/n8n-vs-make-vs-zapier-pick-by-what-you-are-actually-automating-2653</link>
      <guid>https://dev.to/itsnajam/n8n-vs-make-vs-zapier-pick-by-what-you-are-actually-automating-2653</guid>
      <description>&lt;p&gt;All three connect your tools without writing software. They differ in where they run, how they charge and how far they go before you hit a wall.&lt;/p&gt;

&lt;p&gt;Short answer:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Zapier is the quickest to start and the most expensive at volume.&lt;/li&gt;
&lt;li&gt;Make is the best visual builder for branching and reshaping data.&lt;/li&gt;
&lt;li&gt;n8n can run on your own server, so there is no per-run fee and no limit on code steps.&lt;/li&gt;
&lt;li&gt;If the automation is the product, none of the three is the right tool.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  The short answer
&lt;/h2&gt;

&lt;p&gt;For a small business that wants something running this week, Zapier or Make. For an automation that runs thousands of times a day, or that needs a real code step in the middle, n8n. The tool is rarely the reason an automation fails; an unclear rule is.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Pick Zapier if you want it working today, the flow is simple and the volume is low.&lt;/li&gt;
&lt;li&gt;Pick Make if the flow branches and the data needs reshaping, and someone will look at it again.&lt;/li&gt;
&lt;li&gt;Pick n8n if the volume is high, you need a real code step, or you would rather host it yourself.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  How do they compare?
&lt;/h2&gt;

&lt;p&gt;This is the comparison I run through with a client before choosing.&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;What matters&lt;/th&gt;
&lt;th&gt;n8n&lt;/th&gt;
&lt;th&gt;Make&lt;/th&gt;
&lt;th&gt;Zapier&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Where it runs&lt;/td&gt;
&lt;td&gt;Their cloud, or your own server&lt;/td&gt;
&lt;td&gt;Their cloud&lt;/td&gt;
&lt;td&gt;Their cloud&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;How you pay&lt;/td&gt;
&lt;td&gt;By workflow executions on their cloud, nothing extra if you host it&lt;/td&gt;
&lt;td&gt;Per operation, including steps inside a scenario&lt;/td&gt;
&lt;td&gt;Per task, per run&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;How many apps it connects&lt;/td&gt;
&lt;td&gt;Fewer, plus anything with an API&lt;/td&gt;
&lt;td&gt;A large library&lt;/td&gt;
&lt;td&gt;The largest library&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Code in the middle&lt;/td&gt;
&lt;td&gt;A full code node, no limits&lt;/td&gt;
&lt;td&gt;Limited scripting&lt;/td&gt;
&lt;td&gt;A code step with limits&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Branching and reshaping data&lt;/td&gt;
&lt;td&gt;Good, and readable once you know it&lt;/td&gt;
&lt;td&gt;The best of the three&lt;/td&gt;
&lt;td&gt;Simple cases only&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Who can maintain it&lt;/td&gt;
&lt;td&gt;Someone technical&lt;/td&gt;
&lt;td&gt;Someone patient&lt;/td&gt;
&lt;td&gt;Almost anyone&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Moving away later&lt;/td&gt;
&lt;td&gt;Workflows are files you keep&lt;/td&gt;
&lt;td&gt;Scenarios can be exported&lt;/td&gt;
&lt;td&gt;Setups live inside Zapier&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;h2&gt;
  
  
  Where does each one hurt?
&lt;/h2&gt;

&lt;p&gt;Every tool has the same complaint from the same kind of user. Knowing it in advance saves you the migration.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Zapier: the bill grows faster than the business, and multi-step logic gets awkward.&lt;/li&gt;
&lt;li&gt;Make: the visual map becomes hard to read once a scenario has forty modules, and operations are easy to spend without noticing.&lt;/li&gt;
&lt;li&gt;n8n: someone has to look after it, especially if you host it yourself, and non-technical colleagues will not edit it happily.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Where does AI fit in?
&lt;/h2&gt;

&lt;p&gt;All three can call a model, and that is where most of my recent work has been. The useful pattern is not a chatbot: it is a narrow job, like sorting an enquiry, summarising a document or drafting a reply for a person to approve.&lt;br&gt;
I keep the model step inside written limits: what it may decide, what it may never send without a human, and a log of what it was given and what it returned. That is what makes an AI step survivable in a real business.&lt;/p&gt;

&lt;h2&gt;
  
  
  When none of them is the right tool
&lt;/h2&gt;

&lt;p&gt;An automation tool is for moving data between things that already exist. It is the wrong choice when the automation is the product, when the logic is genuinely complex, or when the volume makes a per-run fee silly.&lt;br&gt;
At that point the honest option is a small piece of software with a database, which is also easier to test and cheaper to run. I would rather tell you that on the first call than build something you outgrow in three months.&lt;/p&gt;

&lt;p&gt;Takeaways:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Start with the rule you want automated, not with the tool.&lt;/li&gt;
&lt;li&gt;Count the runs before you pick, because that is what the bill follows.&lt;/li&gt;
&lt;li&gt;Put AI steps behind written limits and a human approval.&lt;/li&gt;
&lt;li&gt;If the automation is the product, build software instead.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Q: Which one do you use most?&lt;br&gt;
A: All three, depending on the job. For a small business that wants to edit things itself, usually Make or Zapier. For volume or anything with a real code step, n8n.&lt;/p&gt;

&lt;p&gt;Q: Can you take over an automation someone else built?&lt;br&gt;
A: Yes. I read it, work out what it does and what breaks when it fails quietly, then tell you whether to tidy it or rebuild it.&lt;/p&gt;

&lt;p&gt;Q: What if the app I use has no integration?&lt;br&gt;
A: Then it probably has an API, and if it does not, there is usually another way in: an export, a webhook, or reading what the app already sends by email.&lt;/p&gt;

&lt;p&gt;Q: Do I own the automation you build?&lt;br&gt;
A: Yes. It is built in an account in your name, so you keep it whether or not I stay on. That is one reason I avoid setups you cannot leave.&lt;/p&gt;

&lt;p&gt;Q: How much does an automation cost to run?&lt;br&gt;
A: The tool's own fee plus any model calls. I work both out from published prices and your volume before I build, so the monthly number is not a surprise.&lt;/p&gt;

&lt;p&gt;Sources:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;n8n documentation: &lt;a href="https://docs.n8n.io/" rel="noopener noreferrer"&gt;https://docs.n8n.io/&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;n8n pricing: &lt;a href="https://n8n.io/pricing/" rel="noopener noreferrer"&gt;https://n8n.io/pricing/&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;Make help centre: &lt;a href="https://help.make.com/" rel="noopener noreferrer"&gt;https://help.make.com/&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;Zapier pricing: &lt;a href="https://zapier.com/pricing" rel="noopener noreferrer"&gt;https://zapier.com/pricing&lt;/a&gt;
&lt;/li&gt;
&lt;/ul&gt;




&lt;p&gt;This is a republished version of a guide from my own site: &lt;a href="https://najam.dev/guides/n8n-vs-make-vs-zapier/" rel="noopener noreferrer"&gt;https://najam.dev/guides/n8n-vs-make-vs-zapier/&lt;/a&gt;. I build these automations for small teams and founders, so if you want a second opinion on which tool fits your case, the contact details are on &lt;a href="https://najam.dev" rel="noopener noreferrer"&gt;https://najam.dev&lt;/a&gt;.&lt;/p&gt;

</description>
      <category>automation</category>
      <category>n8nbrightdatachallenge</category>
      <category>webdev</category>
      <category>beginners</category>
    </item>
    <item>
      <title>I take vibe-coded demos to production. Here is what actually breaks.</title>
      <dc:creator>Muhammad Najam Ul Hassan</dc:creator>
      <pubDate>Sat, 31 Oct 2026 03:15:28 +0000</pubDate>
      <link>https://dev.to/itsnajam/i-take-vibe-coded-demos-to-production-here-is-what-actually-breaks-10bd</link>
      <guid>https://dev.to/itsnajam/i-take-vibe-coded-demos-to-production-here-is-what-actually-breaks-10bd</guid>
      <description>&lt;p&gt;AI can take an idea to a working demo in days. Getting it ready for real payments, real data and the app stores is a different job, and it starts with reading the code.&lt;/p&gt;

&lt;p&gt;Short answer:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;A demo answers whether the idea works. Production answers whether it can hold real users, real money and real data.&lt;/li&gt;
&lt;li&gt;AI tools are confident in the places where a mistake costs the most: permissions, payments, error handling and data access.&lt;/li&gt;
&lt;li&gt;Cleanup is usually cheaper than a rebuild when the data model and the main flows are sound.&lt;/li&gt;
&lt;li&gt;The first step is a code read: a written verdict on what is there, what is missing and which route costs less.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  What is vibe coding cleanup?
&lt;/h2&gt;

&lt;p&gt;Vibe coding is building software by describing what you want to an AI tool and accepting what it writes. It is genuinely fast at reaching a working screen, which is why so many ideas now get their first version this way.&lt;br&gt;
Cleanup is the engineering pass between that demo and a product people can pay for. Someone who did not write the code reads all of it, tests the flows that carry money and data, and fixes the places where it would fail under real use.&lt;br&gt;
It is not a rewrite by default. Most cleanup keeps the screens and the decisions that already work and repairs the parts a demo never had to prove.&lt;/p&gt;

&lt;h2&gt;
  
  
  What are the signs an AI-built app needs cleanup?
&lt;/h2&gt;

&lt;p&gt;An AI-built app can look finished from the outside. These are the signs I look for when someone sends me one to inspect.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Nobody can explain what the database tables are for, or the same fact is stored in two of them.&lt;/li&gt;
&lt;li&gt;Sign-in was added last, so some private screens can still be opened without it.&lt;/li&gt;
&lt;li&gt;Keys or passwords sit in the browser code where any visitor can read them.&lt;/li&gt;
&lt;li&gt;One failed payment or a dropped connection leaves a blank screen.&lt;/li&gt;
&lt;li&gt;There are no tests, so nobody can change a screen without guessing what else breaks.&lt;/li&gt;
&lt;li&gt;The same rule is written in three places and the three versions disagree.&lt;/li&gt;
&lt;li&gt;Nobody has loaded it with more than a handful of records.&lt;/li&gt;
&lt;li&gt;It has never been through store approval, or it was rejected and nobody knows why.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  What does cleanup involve?
&lt;/h2&gt;

&lt;p&gt;The work follows whatever the code read turns up, in the order that removes the most risk first. In most projects it lands in the same few areas.&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Area&lt;/th&gt;
&lt;th&gt;What gets checked&lt;/th&gt;
&lt;th&gt;What usually changes&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Data&lt;/td&gt;
&lt;td&gt;Tables, relationships, duplicates and missing rules&lt;/td&gt;
&lt;td&gt;A structure and migrations that match how the app actually works&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Access&lt;/td&gt;
&lt;td&gt;Sign-in on every private screen, and what each user can see&lt;/td&gt;
&lt;td&gt;Permission checks on the server, not just hidden buttons&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Secrets&lt;/td&gt;
&lt;td&gt;Keys in the browser, in the repository and in the logs&lt;/td&gt;
&lt;td&gt;Keys moved to the server and replaced&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Payments&lt;/td&gt;
&lt;td&gt;Failure, refund, retry and a double tap on Pay&lt;/td&gt;
&lt;td&gt;One payment path with states that can be tested&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Errors&lt;/td&gt;
&lt;td&gt;What a user sees when a request fails&lt;/td&gt;
&lt;td&gt;A message and a retry instead of a blank screen&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Tests&lt;/td&gt;
&lt;td&gt;Which flows are covered and what breaks on change&lt;/td&gt;
&lt;td&gt;Tests on the flows that carry money and data&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Speed&lt;/td&gt;
&lt;td&gt;First load, long lists and a weak connection&lt;/td&gt;
&lt;td&gt;Pagination, caching and lighter screens&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Stores&lt;/td&gt;
&lt;td&gt;Privacy, permissions and store rules&lt;/td&gt;
&lt;td&gt;The settings and disclosures Apple and Google require&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;h2&gt;
  
  
  Cleanup or rebuild: which is cheaper?
&lt;/h2&gt;

&lt;p&gt;A rebuild is not automatically cleaner. Starting again throws away the screens that work and every decision already tested with users, and it can repeat the same mistakes if the plan does not change.&lt;br&gt;
Rebuild when the data model is wrong at the root, when the tool cannot give you usable code, or when every screen depends on every other one and no part has ever been tested. Clean up when the main flows work with real data and the problems are concentrated in a few areas.&lt;br&gt;
A code read decides it. I read the code, test the main flows and write a verdict that prices both routes, whether or not you hire me for the work.&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;What the read finds&lt;/th&gt;
&lt;th&gt;Cleanup&lt;/th&gt;
&lt;th&gt;Rebuild&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Main flows work with real data&lt;/td&gt;
&lt;td&gt;Usually the cheaper route&lt;/td&gt;
&lt;td&gt;Rarely worth starting over&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;The tool cannot export usable code&lt;/td&gt;
&lt;td&gt;Not possible&lt;/td&gt;
&lt;td&gt;Rebuild in code you own&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;The same fact is stored in three tables&lt;/td&gt;
&lt;td&gt;Possible, but expensive&lt;/td&gt;
&lt;td&gt;Often cheaper over time&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;The problems are access, keys and payment states&lt;/td&gt;
&lt;td&gt;This is cleanup work&lt;/td&gt;
&lt;td&gt;A rebuild repeats them unless the plan changes&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;h2&gt;
  
  
  What does vibe coding cleanup cost?
&lt;/h2&gt;

&lt;p&gt;Cleanup is quoted as one fixed price after a code read, because the number follows what is actually in the repository rather than what the demo shows. Small jobs start at $49 for a single fix or a look at one screen.&lt;br&gt;
A cleanup that touches payments, permissions and tests is a build-sized job. It is still usually less than a rebuild, and you keep the parts that already work. The code read is the cheapest way to find out which route you are on, so ask for it before agreeing to any number.&lt;/p&gt;

&lt;h2&gt;
  
  
  Can you work with apps built in Lovable, Bolt, Base44 or Replit?
&lt;/h2&gt;

&lt;p&gt;Yes. What the tool exported matters more than which tool it was. If it gives you a code repository, the cleanup happens in that code and nothing has to be thrown away first.&lt;br&gt;
If it only gives you a hosted app with no usable export, the first job is getting the data out and deciding whether the screens are worth rebuilding. Either way, you end up owning the code, the data and the accounts.&lt;/p&gt;

&lt;h2&gt;
  
  
  What should I prepare before a code read?
&lt;/h2&gt;

&lt;p&gt;The read goes faster when I can see the app as a user sees it and reach the code in the same session.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;A link to the live app, and a test login for each kind of user.&lt;/li&gt;
&lt;li&gt;Access to the code repository, or an export from the tool that built it.&lt;/li&gt;
&lt;li&gt;A short list of what worries you most, even if it is only a feeling.&lt;/li&gt;
&lt;li&gt;The flow that makes money, described in a sentence, so I test that one first.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Takeaways:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;A working demo is the start of the engineering, not the end of it.&lt;/li&gt;
&lt;li&gt;AI writes plausible code. Permissions, payments and failure states still need a person to check them.&lt;/li&gt;
&lt;li&gt;Cleanup beats a rebuild when the data model and the main flows are sound.&lt;/li&gt;
&lt;li&gt;Get a written code read before you agree to a cleanup price or a rebuild.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Q: What is vibe coding cleanup?&lt;br&gt;
A: It is the engineering work that turns an AI-built demo into something safe to charge money for: reading the code, fixing access and payment failures, adding tests and preparing the app for the stores. Most of the time it keeps the screens that already work.&lt;/p&gt;

&lt;p&gt;Q: How do I know if my AI-built app is safe to launch?&lt;br&gt;
A: Try it the way a stranger would. Sign out and open a private screen, pay with a test card and make the payment fail, drop the connection halfway through a form. If any of those breaks the app or shows data it should not, it is not ready.&lt;/p&gt;

&lt;p&gt;Q: Can you clean up an app built with Lovable, Bolt, Base44 or Replit?&lt;br&gt;
A: Yes. If the tool exported a code repository, the work happens in that code. If it only gave you a hosted app, the first job is getting the data out and deciding whether the screens are worth rebuilding.&lt;/p&gt;

&lt;p&gt;Q: Will cleanup break the features that already work?&lt;br&gt;
A: It should not, and that is why tests come early. Each feature that stays gets a test before it is touched, so a change that breaks something is caught before your users see it.&lt;/p&gt;

&lt;p&gt;Q: How long does a cleanup take?&lt;br&gt;
A: Days for a small app with one broken area, weeks when access, payments and tests all need work. The code read gives you a date and a fixed price before the work starts.&lt;/p&gt;

&lt;p&gt;Q: Should I rebuild instead of cleaning up?&lt;br&gt;
A: Only when the data model is wrong at the root, the tool cannot export usable code, or nothing has ever been tested. A rebuild costs more and takes longer, so it should be the answer the code gives, not the safe default.&lt;/p&gt;

&lt;p&gt;Q: Will I lose users or data during a cleanup?&lt;br&gt;
A: No. The database stays in place, and any change to its structure is planned and run against a copy first. Your users keep using the app while the work happens.&lt;/p&gt;

&lt;p&gt;Sources:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Submitting an app to the App Store: &lt;a href="https://developer.apple.com/app-store/submitting/" rel="noopener noreferrer"&gt;https://developer.apple.com/app-store/submitting/&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;Google Play Developer Policy: &lt;a href="https://play.google.com/about/developer-content-policy/" rel="noopener noreferrer"&gt;https://play.google.com/about/developer-content-policy/&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;OWASP Top 10: &lt;a href="https://owasp.org/www-project-top-ten/" rel="noopener noreferrer"&gt;https://owasp.org/www-project-top-ten/&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;Stripe security documentation: &lt;a href="https://docs.stripe.com/security" rel="noopener noreferrer"&gt;https://docs.stripe.com/security&lt;/a&gt;
&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  FAQ
&lt;/h2&gt;




&lt;p&gt;This is a republished version of a guide I wrote for my own site, and the original lives at &lt;a href="https://najam.dev/guides/vibe-coding-cleanup/" rel="noopener noreferrer"&gt;https://najam.dev/guides/vibe-coding-cleanup/&lt;/a&gt;. If you have an AI-built app and are not sure whether it can take payments or pass store review, the fastest way to find out is a code read. My contact details are on &lt;a href="https://najam.dev" rel="noopener noreferrer"&gt;https://najam.dev&lt;/a&gt;.&lt;/p&gt;

</description>
      <category>webdev</category>
      <category>ai</category>
      <category>programming</category>
      <category>beginners</category>
    </item>
  </channel>
</rss>
