And Zeros Logo
  • Home
  • About
  • Services
    • Branding
    • Platform
    • Growth
    • AI SEO
      • AEO
      • GEO
  • Portfolio
  • Zero Crossing
  • Contact
    Contact
    Location:
    Santa Fe, New Mexico
    Email:
    hello@andzeros.com
    Phone:
    ‪(505) 395-6413‬
    LinkedinInstagram
    Get in Touch

    • Subscribe
    Subscribe
    And Zeros Logo
    • Home
    • About
    • Services
      • Branding
      • Platform
      • Growth
      • AI SEO
        • AEO
        • GEO
    • Portfolio
    • Zero Crossing
    • Contact
      Contact
      Location:
      Santa Fe, New Mexico
      Email:
      hello@andzeros.com
      Phone:
      ‪(505) 395-6413‬
      LinkedinInstagram
      Get in Touch

      • Subscribe
      Subscribe
      • Home
      • About
      • Services
        • Branding
        • Platform
        • Growth
        • AI SEO
          • AEO
          • GEO
      • Portfolio
      • Zero Crossing
      • Contact
        Contact
        Location:
        Santa Fe, New Mexico
        Email:
        hello@andzeros.com
        Phone:
        ‪(505) 395-6413‬
        LinkedinInstagram
        Get in Touch

        • Subscribe
        Development
        HomeArchive by Category "Development"

        Category: Development

        how long does it take to build a website
        Development
        October 29, 2026By Doug Saltzman

        How Long Does It Take to Build a Website?

        How long does it take to build a website? It is the second question every business owner asks, right after cost. The honest answer depends less on your developer and more on how ready you are on day one.

        In audio, a session runs on time when the charts are written before the band walks in. Web builds work the same way. The hours at the keyboard are predictable. The waiting is what stretches a project.

        How long does it take to build a website in 2026?

        Timelines have shrunk. A 2019 G2 guide estimated that an agency build would take at least 18 weeks. Today, Elementor’s 2026 timeline guide puts a professional small business site at 4 to 8 weeks. Better tools and tighter processes made up most of that gap.

        Here is how the 2026 estimates break down by site type, for professional builds:

        Site typeTypical scopeProfessional timeline
        Brochure site1 to 5 pages1 to 2 weeks
        Small business site5 to 15 pages, blog, forms4 to 8 weeks
        Small e-commerce storeUnder 50 products8 to 12 weeks
        Large e-commerce store500+ products4 to 8 months
        Custom web applicationLogins, data, integrations6 to 12+ months

        Most service businesses land in the small business row. That covers a home page, service pages, an about page, a blog and a contact form.

        What are the phases of a website build?

        A website build moves through six phases. Some overlap, and content can run alongside design. These ranges come from Elementor’s 2026 phase breakdown:

        1. Strategy and planning, 1 to 2 weeks. Goals, audience, sitemap and wireframes.
        2. Design, 1 to 4 weeks. Mockups and revision rounds. Fast feedback keeps this near one week.
        3. Development, 1 to 8+ weeks. Pages, forms, integrations and any custom features.
        4. Content, 1 to 3 weeks. Final copy, photos and image compression.
        5. Testing, 1 to 2 weeks. Browsers, phones, forms, speed and accessibility.
        6. Launch, 1 day to 1 week. Go-live, redirects, sitemap submission and analytics checks.

        Run back to back, those ranges add up to about 5 weeks to 5 months. The phases with the widest spread are design and development. Both swing on feedback speed and scope.

        How long does it take to build a website? Infographic showing six development phases, from strategy and design to testing and launch, with estimated timelines.

        What slows down a website project?

        Content is the top cause of delays. Elementor’s guide names missing copy and images as the biggest reason projects stall, with scope creep in second place. A finished design can sit for weeks while a team writes its About page.

        Approvals come next. Every round of design feedback waits on someone. One decision maker might reply in a day. A committee of five can take a week per round, and a build often needs more than one round.

        Scope creep is the third. A request like “can we add member logins?” sounds small. In practice it can add weeks of development and testing.

        Technical surprises matter less than most people expect. Old domain logins, lost hosting access and missing brand files cause more lost days than code.

        How long does an And Zeros website build take?

        We run three build tracks. Each one ships a finished, tested site. The difference is how much has to be ready before we start.

        Standard build: 2 months

        This is our default for service businesses. Eight weeks gives room for discovery, two design rounds, a full build and real testing. It also leaves space for your team to write content while we design. Most clients pick this track.

        Expedited build: 1 month

        The expedited track compresses the same process into four weeks. It works when your content is mostly ready and one person can approve design within a day or two. We overlap design and development to save time.

        Extreme sprint: 2 weeks

        The sprint is for launches with a hard date, like an event, a rebrand reveal or a funding round. It needs final content on day one and same-day feedback. The scope stays tight, so extra features wait for a second phase after launch.

        Every track includes one month of support after launch. That covers the stretch when post-launch issues tend to show up.

        How can you build a website faster?

        Start with content. If your copy and photos are final before kickoff, you can cut weeks from any timeline. Elementor’s guide calls this the most important step you can take.

        Next, name one decision maker. A single person with authority to approve design keeps revision rounds short.

        Then lock the scope. Write down the pages and features you need for launch. Park everything else on a phase two list.

        Last, gather your access early. Domain registrar logins, hosting accounts, Google Analytics and brand files should be in one place before day one.

        Does a faster build hurt SEO?

        A fast build only hurts SEO when steps get skipped. Redirects, title tags, schema and page speed take hours of work. They do need to be on the plan.

        Rebuilds carry the most risk. An old site’s rankings live in its URLs, and a missing redirect map can erase them at launch. We cover that process in our website redesign SEO guide. On a sprint, the redirect map gets built in week one, before any page goes live.

        Planning a new site with a launch date in mind? Talk to us about which track fits.

        FAQ

        How long does a website take to build with a website builder?

        A simple site on a website builder can launch in 1 to 3 days. That assumes a template and finished content. A 5 to 15 page small business site usually takes 1 to 2 weeks on your own.

        How long does it take to build an e-commerce website?

        A small e-commerce store with under 50 products takes 8 to 12 weeks with a professional. Large stores with 500 or more products and inventory integrations can take 4 to 8 months.

        How long does it take to build a Shopify website?

        A basic Shopify store can launch in a few weeks. Timelines grow with product count, custom theme work and app integrations. Product photos and descriptions are the usual bottleneck.

        Can a website be built in two weeks?

        Yes, a professional website can be built in two weeks with tight scope and ready content. It needs final copy and photos on day one, same-day feedback and a short feature list.

        What is the biggest cause of website delays?

        Late content is the biggest cause of website delays. Copy and images often take longer to finish than design and development. Having them ready before kickoff is the fastest way to shorten any build.

        Read More
        WebMCP connecting a business website's quote request form to an AI agent for automated form completion.
        DevelopmentAI
        October 22, 2026By Doug Saltzman

        What Is WebMCP? Making Your Website Agent-Ready

        What Is WebMCP? How to Make Your Website Agent-Ready

        WebMCP is a proposed web standard that lets a website hand AI agents a list of actions it supports, like “search products” or “request a quote,” with the exact inputs each one needs. Agents call those actions directly instead of guessing at buttons. Chrome is testing it now, and Shopify switched it on for every Liquid store in August.

        Before 1983, a Roland synth and a Sequential synth had no shared language. If you wanted one to follow the other, you recorded it and played the part again by hand. MIDI changed that. Note on, note off, how hard the key was hit: one cable, and the second instrument knew exactly what to play.

        WebMCP is that cable for websites and AI agents. Today, an agent booking a table or requesting a quote on your site does the microphone version. It takes screenshots, reads the page code, guesses which field wants a phone number and hopes the blue button is the submit button. WebMCP gives your site a port the agent can plug into instead.

        What is WebMCP?

        WebMCP (Web Model Context Protocol) is a browser standard that lets a page declare what an agent can do on it. Engineers from Google and Microsoft are writing it through the W3C Web Machine Learning Community Group. Google’s Chrome team opened an early preview on February 10, 2026.

        A site registers “tools.” Each tool has a name, a plain-language description and a JSON Schema that lists its inputs. An agent visiting the page reads that list and calls the tool it needs. People still see the same site. Chrome’s documentation calls this a progressive enhancement, so browsers without support simply ignore it.

        The name borrows from MCP, the Model Context Protocol, which connects AI apps to back-end systems through a server. WebMCP runs inside the browser tab and uses the visitor’s live session. Nothing new runs on your server.

        How does WebMCP work on a website?

        There are two ways to add it. The declarative API turns an existing HTML form into a tool with two attributes on the <form> tag: toolname and tooldescription. The imperative API uses JavaScript, through document.modelContext.registerTool(), for actions that aren’t forms, like product filters, a cart or a date picker.

        Here’s a quote request form with the declarative attributes added:

        <form toolname="request_quote"
              tooldescription="Request a project estimate from our team."
              action="/quote">
          <label for="name">Your name</label>
          <input id="name" name="name" required>
          <label for="service">Service</label>
          <select id="service" name="service" required>
            <option>Website redesign</option>
            <option>SEO retainer</option>
          </select>
          <button type="submit">Send request</button>
        </form>

        Look at what does the heavy lifting there. It’s the labels. Chrome builds each input’s description from its <label>, and falls back to aria-description when there isn’t one. Swap labels for placeholder text and the form gets harder to use. That’s true for a person on a screen reader and for an agent.

        By default, the agent fills the form and the person clicks submit. A toolautosubmit attribute lets the agent submit on its own, which makes sense for a site search and not much else. While an agent works, Chrome outlines the form so the visitor can see what’s happening.

        Who supports WebMCP right now?

        Support grew fast in late summer. Chrome moved WebMCP into a public origin trial starting with Chrome 149. Sites can now run it for real visitors by registering a trial token.

        Date (2026)WhoWhat happened
        Aug 25OpenAIThe ChatGPT desktop app’s browser added WebMCP as “site tools,” for GPT-5.6 Sol and Terra (not Enterprise or Edu workspaces)
        Aug 21ShopifyWebMCP tools went live on every Liquid storefront: catalog search, cart and checkout, with nothing to install
        Aug 6CloudflareDeveloper preview: one dashboard switch adds WebMCP tools to a site with no code changes
        May 19GoogleChrome 149 origin trial announced at Google I/O, with Gemini in Chrome support to follow
        Feb 10GoogleEarly preview behind a Chrome flag

        Firefox and Safari haven’t said anything public yet. Microsoft co-wrote the spec, but Edge support isn’t confirmed in its release notes.

        So far the supply has outrun the demand. Chrome’s docs list discoverability as a limitation: an agent has to visit your site before it knows your tools exist. WebMCP has no effect on how agents find you. Its job starts once an agent lands on your page.

        Does WebMCP help SEO or AI search visibility?

        Not directly. Google hasn’t announced any ranking connection, and WebMCP tools are invisible until an agent is already on the page. Getting cited by ChatGPT or showing up in an AI Overview still depends on content, entity signals and structured data.

        WebMCP sits one step later in the funnel. Say an AI assistant recommends your business and the user tells it to book a consultation. Can the agent finish the job, or does it stall on your form? That’s a conversion question, and conversion is where web development earns its keep.

        How WebMCP makes a website agent-ready by exposing HTML forms as tools that AI agents can understand and complete.

        What makes a website agent-ready?

        An agent-ready website is one an agent can operate without guessing. Most of that work is plain, well-built HTML, which is good news, because it also helps every human visitor.

        Forms built on real HTML

        Every field needs a <label>, the right input type (email, tel, date) and a clear required state. Dropdown options should say what they mean. This is accessibility work you should be doing anyway, and WebMCP rewards it twice.

        Forms that live on your own domain

        Many sites embed scheduling or quote widgets from a third party inside an iframe. WebMCP’s permissions policy blocks tool registration in cross-origin iframes unless the embed allows it, and you don’t control that vendor’s markup. If your booking flow matters, it should run on your own pages.

        Tool names and descriptions written like good copy

        A model reads your tooldescription cold. “Submit” tells it nothing. “Request a project estimate for a website or SEO engagement” tells it when to use the tool. It’s the same discipline as writing a meta description, aimed at a different reader.

        A human confirmation step for anything that matters

        Keep the default for bookings, deposits and purchases: the agent fills, the person confirms. ChatGPT’s site tools already ask before purchases, account changes or sharing personal information, and your site should hold the same line.

        When we build a site, the forms get the same attention as the homepage, because that’s where leads arrive. You can see how that plays out across recent builds in our portfolio.

        Should your business add WebMCP now?

        It depends on what your site runs on and what visitors do there.

        Your siteWhat WebMCP means todayWhat to do
        Shopify store on a Liquid themeAlready on. Agents can search, add to cart and reach checkoutClean up product titles, variants and policy pages, since agents read them
        Shopify store on production HydrogenNot on yet (only the Hydrogen developer preview has it)Wait for Shopify, or plan it into your next release
        Site behind CloudflareOne switch, but the preview’s packs cover image credentials and your own MCP serverFine to test; it won’t expose your forms by itself
        WordPress or custom site with a booking or quote formNothing yetAdd toolname and tooldescription to that form at your next update
        Brochure site with a phone number and email linkLittle to exposeSpend the effort on content, schema and a real contact form

        For a service business, the declarative attributes are a small, low-risk change. Browsers without support ignore them. The bigger win is the form audit that should come first.

        In audio, you make an edit at the zero crossing, where the waveform passes through silence, so the cut doesn’t click. Agent traffic is still small. Fixing your forms now is the clean edit, done before the volume comes up.

        FAQ

        Is WebMCP the same as MCP?

        No. MCP connects AI apps to back-end systems through a server, while WebMCP runs inside the browser tab. A WebMCP tool lives in your page’s own code and uses the visitor’s signed-in session. You don’t deploy anything new on your server to support it.

        Does my small business website need WebMCP?

        Most small business sites don’t need WebMCP today, but they do need forms an agent can read. Labeled fields, correct input types and a booking flow on your own domain come first. Once those are solid, adding toolname and tooldescription to a key form takes minutes.

        Does WebMCP work with ChatGPT?

        Yes. Since August 25, 2026, the browser inside the ChatGPT desktop app supports WebMCP under the name “site tools.” OpenAI lists GPT-5.6 Sol and Terra as supported, and site tools aren’t available in Enterprise or Edu workspaces. In Chrome, Gemini is the agent expected to call these tools.

        Is WebMCP safe for my website?

        WebMCP keeps the person in control by default: the agent fills a visible form, and the person clicks submit. Chrome outlines the form while an agent works on it. Chrome’s security guidance also warns about tool descriptions being used to mislead agents, so only expose actions you’d be comfortable letting a stranger’s assistant attempt.

        How do I test WebMCP on my site?

        You can test WebMCP locally by turning on the chrome://flags/#enable-webmcp-testing flag in Chrome. Google’s Model Context Tool Inspector extension then shows the tools your page registers and lets you call them. To run WebMCP for real visitors, register your domain for the Chrome origin trial.

        Read More
        Website redesign SEO concept: an audio waveform with an edit marker placed on the zero crossing
        DevelopmentSEO
        October 8, 2026By Doug Saltzman

        Redesigning Your Website Without Losing SEO Rankings

        Every audio editor learns one rule early. Cut a waveform anywhere but the zero crossing and you hear a click. Website redesign SEO works the same way. Launch a new site at the wrong point in the wave and the pop shows up in your traffic reports for months.

        Redesigning your website for SEO means protecting the signals your current site has already earned before you launch the new one. That takes a full URL map with page-level 301 redirects, server-rendered content that AI crawlers can read, and schema carried over intact. Skip any of those and the new site starts from a deficit.

        • Map every old URL to one new URL and 301 it.
        • Keep redirects live for at least a year, per Google.
        • Serve body copy, navigation and schema in the raw HTML so GPTBot and ClaudeBot can read them.
        • Change one big thing at a time when a domain move is involved.

        Those four steps protect both audiences a site now serves: Googlebot, and the AI crawlers behind ChatGPT, Claude and Perplexity.

        Why do websites lose traffic after a redesign?

        Google stores what it knows about your site one URL at a time. Links, rankings and relevance all attach to a specific address. Change that address with no redirect and the history stays behind on a page that now returns a 404.

        Google’s site move guide is direct about the fix. Map old URLs to new ones, then use permanent redirects like 301 or 308, which Google says “don’t cause a loss in PageRank.” The same guide says to change one thing at a time, and to finish a domain move before you change the layout.

        Most redesigns break that rule. A new domain, a new CMS, a new URL structure and a new design all ship on one launch day. Then nobody can tell which change caused the drop.

        How long does SEO take to recover after a site migration?

        For domain moves, the honest answer is longer than most owners expect. Dan Taylor’s study in Search Engine Journal tracked 892 domain migrations. The average site took 523 days to match its old domain’s estimated organic traffic. 17% still had not caught up after 1,000 days.

        The fastest sites recovered in 19, 22, 23 and 33 days. That spread tells you most of the outcome comes down to execution. Google’s own guidance says a medium site can take “a few weeks or more” before new URLs start to show, and redirects should stay up “generally at least 1 year.”

        A redesign that keeps the same domain usually carries less risk than a full domain move. Still, the same rules apply to every URL you change.

        Can AI search engines read your new website?

        Many can’t, if the content only appears after JavaScript runs. Vercel measured AI crawler traffic across its network in December 2024. GPTBot made 569 million fetches in a month, and Claude’s crawler made 370 million. Vercel found that none of the major AI crawlers render JavaScript, including GPTBot, ChatGPT-User, OAI-SearchBot, ClaudeBot and PerplexityBot.

        They do download script files. ChatGPT’s crawler fetched JavaScript in 11.50% of requests and Claude’s in 23.84%. Neither ran a line of it. Gemini is the exception, since it uses Google’s rendering infrastructure.

        So a site built as a client-side app can look perfect in Chrome and rank fine in Google, yet show up nearly blank to ChatGPT. Test your own pages with a plain request: curl -A "GPTBot" https://yoursite.com/page. If your headline and body copy are missing from the response, AI search can’t cite them.

        Redirects matter here too. In Vercel’s data, ChatGPT’s crawler hit 404s on 34.82% of fetches, against 8.22% for Googlebot. A redesign that drops old URLs adds more dead ends to a crawler that already wastes a third of its visits.

        What should a website redesign SEO checklist include?

        This is the cutover plan we run on And Zeros builds.

        1. Crawl the live site and export every indexable URL. Pull top landing pages from Search Console across its full 16 months of data.
        2. Build a one-to-one redirect map. Each old URL points to its closest new match. Never send everything to the homepage.
        3. Freeze title tags, H1s and core copy on your top pages for launch. Rewrite them after the new site settles.
        4. Pick a build that serves full HTML: server-side rendering, static generation or prerendering.
        5. Carry over schema (Organization, Service, Article, FAQPage) and confirm it appears in the raw HTML.
        6. Lock staging behind a password, then confirm noindex is gone at launch.
        7. Submit the new XML sitemap on launch day. Use Search Console’s Change of Address tool if the domain changed.
        8. Watch for 90 days. Crawl for 404s weekly, compare landing pages to your baseline, and check brand prompts in ChatGPT and Perplexity.
        Side-by-side view of one web page as Googlebot renders it and as GPTBot reads the raw HTML, with the body copy missing

        What should you ask a web agency before a redesign?

        Most small businesses aren’t asking yet. Bluehost’s State of Small Business AI Confidence report surveyed 350 U.S. owners in May 2026. Only 13% actively optimize for AI search. Another 31% know it exists but don’t know where to start.

        That gap shows up in redesign proposals. Before you sign one, ask:

        • Who builds the redirect map, and when do we review it?
        • What does our homepage show with JavaScript turned off?
        • Which schema types carry over, and how will you test them?
        • What happens if organic traffic drops 20% after launch?

        A good agency answers each with a name and a date. At And Zeros, every web build includes six months of support after launch. That window covers the stretch where migration problems tend to surface. If you’re planning a website rebuild, talk to us before the cut.

        FAQ

        Does a website redesign hurt SEO?

        A website redesign hurts SEO only when ranking signals get lost at launch. Missing redirects, changed URLs, deleted pages and stripped content cause most drops. A planned cutover with a full redirect map can hold rankings steady or improve them.

        How long should I keep 301 redirects after a redesign?

        Keep 301 redirects for at least one year, and longer if you can. Google’s site move guide says to keep them “for as long as possible, generally at least 1 year” so it can recrawl old links and transfer signals.

        Do ChatGPT and Claude crawlers run JavaScript?

        No, ChatGPT and Claude crawlers do not run JavaScript. Vercel’s December 2024 data shows GPTBot, ClaudeBot and PerplexityBot fetch script files without executing them. Content that only loads through JavaScript stays invisible to them.

        Should I change my domain and redesign at the same time?

        Google advises against changing your domain and design at the same time. Its site move guide recommends one change at a time, finishing the domain move before the layout changes. Splitting them makes any traffic drop easier to diagnose.

        How long does a site migration take to recover?

        A well-run site migration can recover in weeks, but the average domain move takes far longer. Search Engine Journal’s study of 892 domain migrations found an average of 523 days, with the fastest at 19 days.

        Read More
        Abstract Zero Crossing-inspired workspace scene featuring wireframe sketches, concrete architectural forms, dark industrial textures, and orange accents representing the evolution from website design to application architecture.
        Development
        June 16, 2026By Doug Saltzman

        The Website That Was Secretly an Application

        A prospect came to us last month with a site they’d put together over a weekend. It looked good. Fast, clean, the copy actually said something. About ten minutes into the call they mentioned, kind of offhand, that it was already taking orders and holding people’s card details.

        I sort of stopped them there. Because the thing they were describing wasn’t really a website anymore, and I don’t think anyone had pointed that out to them. They’d set out to build a website and somewhere along the way built an application instead, without ever deciding to.

        I want to be careful here because this turns into a tools complaint really fast and that’s not what I’m getting at. The tools are good now. Insanely good. You describe what you want and it shows up, and for a marketing page or a portfolio that’s usually fine. Genuinely fine. A lot of the work agencies used to charge for at that level is just gone, and I’m not going to pretend that’s a tragedy. If you can build your own about page on a Sunday, build your own about page on a Sunday.

        The part that gets people is that the same tool will build you a checkout with the same shrug, and it’ll come out looking just as finished as everything else.

        That’s the whole thing I keep running into. A website mostly shows you stuff. It lays content out, it loads, and when it breaks the worst case is that something looks wrong for a bit. Annoying, fixable, nobody loses anything. But the moment a site starts doing things that stick around after you close the tab, logging people in, moving money, holding data that has to still be right next week, you’re somewhere else entirely. When that breaks you don’t catch it in a preview. You hear about it from a customer who got charged twice, and by then it already happened.

        Here’s what I think actually changed, and why this is a now problem and not a forever one. For most of the time I’ve done this, looking done and being done were the same. The only way to make something look finished was to finish it, so the polish told you something true about what was underneath. That’s not the case anymore. You can get the polish without the rest of it, and the polish shows up first. So the moment you feel best about the thing, the demo runs clean, everyone nods, it looks great, is also the moment you know the least about whether it’ll hold.

        I think about it as the part you can see versus the part you can’t. The demo is the bit on screen. The part that decides whether this survives a busy Tuesday is the bit that isn’t on screen, and you can’t really judge what isn’t there. The page renders, the button works, the obvious path is smooth, and there’s just no visual tell for the order that double-charges at scale or the data that quietly goes sideways when two people hit it at the same second.

        The crossing almost never happens on purpose, which is what makes it sneaky. Nobody decides to turn their website into an application. It goes one sensible little feature at a time. You add accounts, so now you own logins and sessions and the guy who forgot his password. You add payments, so now a bug isn’t a typo, it’s money going the wrong way to actual customers. You start storing things people expect to stay accurate, and “works on my machine” stops meaning anything because the real question is whether it’s still right after a few thousand writes you never watched happen. Any one of those and the rules quietly change underneath you, and “it looks done” stops being worth much, because the thing that can go wrong isn’t the thing you can see.

        So if you’re building something right now, the move isn’t to decide the tools are good or bad. They’re fine, I use them. Not for final products but for ideas and brainstorming. The move is to be honest with yourself early about which thing you’re actually making, before there’s real data sitting in it. If it just shows stuff, go nuts, ship it by lunch if you’re feeling it. If it does anything that has consequences, the part you can’t see is the part that matters, and that’s the part I’d slow down on. It’s important to remember that having it generated and actually understanding it when it breaks at 11pm are not the same situation, and you find out which one you’re in at the worst possible time.

        That prospect’s a client now. We didn’t rebuild their site, we rebuilt the part that had turned into an application and left the part that was honestly still just a website alone. Figuring out where that line fell was most of the job.

        Hopefully this helps answer the important questions early to avoid chaos down the road.

        Read More
        Vibe coding scales until it doesnt
        DevelopmentAI
        May 5, 2026By Doug Saltzman

        Vibe Coding Scales… Until It Doesn’t

        The speed is real.

        I want to say that upfront because this isn’t a post about why AI-assisted development is dangerous or overhyped. We use it and it’s changed how fast we can move and for certain things that’s been genuinely valuable.

        I’m writing this because we’ve had a version of the same conversation three or four times in the last year with founders who built something fast, launched it, grew it, and then hit a wall that cost them significantly more to fix than it would have cost to avoid.

        The pattern is always roughly the same.

        It starts with the demo working.

        Week one is great. The thing runs and it does what it’s supposed to do. The AI helped you move fast and the fast movement felt like the right call because you needed to validate the idea before investing heavily in the infrastructure.

        That part is fine.

        That part is actually correct.

        Then you add one more feature.

        And another. And a third-party integration because the native solution was going to take two weeks and the bolt-on took two hours. And a workaround that one developer understood completely but never wrote down because there wasn’t time.

        None of these decisions are wrong in isolation. Each one made sense given the deadline, the budget, the priorities that week. The problem is that they compound. Every shortcut that worked in the demo becomes an assumption baked into the system. Every undocumented decision becomes a puzzle for whoever touches the code next. Every patch that fixed the immediate problem without addressing the underlying one sits there quietly until something forces the reckoning.

        The reckoning usually arrives when you hire someone or when traffic spikes or when a client asks for something that should be simple and suddenly nothing is simple.

        By that point the person who understood how everything fit together has mentally moved on. The system works until it doesn’t and when it stops working nobody knows where to start. What you have isn’t a product anymore. It’s a patchwork that requires institutional memory to operate.

        That’s when you call someone like us and we look at it and have to tell you that the fix costs more than the original build.

        Engineering discipline doesn’t mean slow.

        It doesn’t mean months of planning before you write a line of code. It means someone on your team is thinking one level above the immediate problem.

        What does this decision mean three months from now?

        What would a new developer need to know to understand why this works the way it does?

        What are we cutting corners on intentionally versus accidentally?

        Those questions don’t take long and skipping them consistently is what gets expensive.

        Build fast. Use the tools. Ship the damn thing. Just make sure what you’re building can carry the weight of what you keep adding to it.

        We build and maintain web and platform systems for growing businesses. If your stack is starting to feel held together with good intentions, let’s talk.

        Read More
        logotype

        Boutique digital marketing rooted in Santa Fe.

        Hostinger Partner

        Services

        Branding

        Growth

        Platform

        AEO

        GEO

        AI SEO

        Contact

        Santa Fe, New Mexico

        hello@andzeros.com

        (505) 395-6413‬

        Working hours

        Mon – Fri : 9am-5pm

        Social

        LinkedinInstagram

        Copyright © 2026 And Zeros LLC. All Rights Reserved.