<?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 Iqbal</title>
    <description>The latest articles on DEV Community by Muhammad Iqbal (@muhammadiqbal_aiweb).</description>
    <link>https://dev.to/muhammadiqbal_aiweb</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%2F4244853%2F790b380e-bad4-45e9-9548-d2a743820df8.png</url>
      <title>DEV Community: Muhammad Iqbal</title>
      <link>https://dev.to/muhammadiqbal_aiweb</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/muhammadiqbal_aiweb"/>
    <language>en</language>
    <item>
      <title>How I Scope an AI Website Before Writing Any Code</title>
      <dc:creator>Muhammad Iqbal</dc:creator>
      <pubDate>Sat, 14 Nov 2026 17:50:41 +0000</pubDate>
      <link>https://dev.to/muhammadiqbal_aiweb/how-i-scope-an-ai-website-before-writing-any-code-i5l</link>
      <guid>https://dev.to/muhammadiqbal_aiweb/how-i-scope-an-ai-website-before-writing-any-code-i5l</guid>
      <description>&lt;p&gt;Most AI web projects that go wrong don't fail on code. They fail because nobody wrote down what "done" means. Here is the checklist I use with every client before I open an editor.&lt;/p&gt;

&lt;h2&gt;
  
  
  1. Name the one AI workflow
&lt;/h2&gt;

&lt;p&gt;I ask the client to finish this sentence: "The user puts in ___ and gets back ___."&lt;/p&gt;

&lt;p&gt;Examples: "Upload a contract PDF -&amp;gt; list of key dates and risks." "Ask a question about our services -&amp;gt; answer with a link to the page it came from."&lt;/p&gt;

&lt;p&gt;If the sentence needs an "and also", that's a second workflow and a second line in the quote.&lt;/p&gt;

&lt;h2&gt;
  
  
  2. Collect real sample inputs
&lt;/h2&gt;

&lt;p&gt;I ask for 5-10 real examples, plus what a good answer looks like for at least two of them. These become the test cases. It turns "the AI should be smart" into something both of us can check.&lt;/p&gt;

&lt;h2&gt;
  
  
  3. Decide the fallback
&lt;/h2&gt;

&lt;p&gt;What should happen when the model isn't sure? For customer-facing assistants, the answer is almost always: say so, and offer a human. I write that into the scope.&lt;/p&gt;

&lt;h2&gt;
  
  
  4. Estimate the running cost
&lt;/h2&gt;

&lt;p&gt;The client pays the model provider directly, on their own API key. Before building, I estimate monthly usage from their expected users and set a per-user daily limit in the app, so one busy day can't produce a surprise bill.&lt;/p&gt;

&lt;h2&gt;
  
  
  5. Agree where everything lives
&lt;/h2&gt;

&lt;p&gt;Code in the client's GitHub. Hosting and database (usually Vercel and Supabase) on the client's accounts. API keys added by the client, not pasted into chat. Handover is then a checklist, not a negotiation.&lt;/p&gt;

&lt;h2&gt;
  
  
  6. Write the "not included" list
&lt;/h2&gt;

&lt;p&gt;Payments, extra pages, scanned PDFs that need OCR, more languages. Writing these down early is what keeps a 7-day project a 7-day project.&lt;/p&gt;

&lt;h2&gt;
  
  
  The stack I use for most AI websites
&lt;/h2&gt;

&lt;p&gt;Next.js and React on the front end, Node.js or Python (FastAPI) on the back end, PostgreSQL via Supabase, OpenAI, Claude or Gemini for the model, Stripe for payments, Vercel for hosting.&lt;/p&gt;

&lt;p&gt;Here's the whole process as a 40-second video:&lt;/p&gt;

&lt;p&gt;  &lt;iframe src="https://www.youtube.com/embed/YSp0fGac1kw" width="710" height="399"&gt;
  &lt;/iframe&gt;
&lt;/p&gt;

&lt;p&gt;If you'd rather have it built for you, I take AI website projects on &lt;a href="https://www.fiverr.com/salarahmad_87/design-a-response-wordpress-website-and-development-in-24-hours" rel="noopener noreferrer"&gt;Fiverr&lt;/a&gt;.&lt;/p&gt;

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