How we build, and how we check it

What this page is, and what it is not

A project scope defines the features included in a custom website or tool. A project does not need every feature listed here. We agree on what the business needs before choosing the parts of the build.

A local owner needs clear service information and a useful path to contact. A technical reader may also want to understand the implementation and the checks required before launch. This page covers both.

We use the business's actual facts and approved material. We do not invent reviews, credentials, screenshots, or results to fill a page. The proposed scope makes clear which features are included.

Start with what we have actually built

Here are two examples of tools we have built.

A scripted chat concierge for a Marco Island boat-tour company. It answers guest questions with owner-approved answers only. It does not improvise. If we have not written and approved a response to a question, the tool does not guess, and it will not invent a price, a policy, or a departure time to fill the silence. That constraint is the entire point. A chat tool that occasionally makes something up is worse than no chat tool at all, because the one time it is wrong is the time it can cost the owner a customer. So we built it to stay inside the lines, and the owner controls every line.

First-party lead dashboards on sites we manage. These report the visits and interactions the tracking records, such as phone-link taps and form activity. A tap does not prove a connected call, and a submitted form still needs follow-up to determine whether it is a qualified inquiry.

Those are two examples of custom tools we have built. The checks described below are requirements for current work, rather than a claim that these earlier builds passed this exact process.

If you want the plain-English tour of the parts those examples are built from, they live under custom tools and lead generation.

How the work actually gets made

Brandon uses software systems he built himself for research, first drafts, page building, and quality checks. The final check is always a person.

The build requirements include:

• The project in view. Check changes against the existing files and source chain so unrelated work is preserved.
• A real browser. Load pages, click links and buttons, exercise forms, and inspect the result at phone and desktop widths.
• Readable content. Important page content must be present in served HTML, with a static fallback for features that depend on JavaScript.
• Review before release. Record the checks and unresolved issues before the business owner reviews the work and approves a release.

A preview lets you inspect the proposed work before it goes public. The broader service is described under web development.

The stack, and why its range matters to you

The scope determines the implementation. Straightforward service pages need readable content and clear contact paths. A tool or store may need additional data, controls, and checkout behavior.

Options we can discuss include:

• Cloudflare edge delivery. A distributed network serves the website rather than a single server the business maintains.
• React and static pages. Interactive interfaces can use React, while important content is also present in the served HTML.
• Data and storage. The quote defines what information the tool needs, where it is stored, and who needs to use it.
• Hosted checkout. Custom store work can use Stripe or Authorize.Net, with the chosen processor and scope recorded in the quote.

Other requests are scoped to the job:

• Interactive maps, configurators, and estimators. Built to answer a useful customer question, with an accessible alternative for the information.
• Staff or customer portals. Start with what each person needs to see and do, then agree on the access requirements.
• Scripted guides. Owner-approved answers and choices help a visitor find information. The concierge example above uses a script, not generated answers.
• Order and document workflows. Define the steps the team needs, such as preparing an order or a client-ready sheet.
• Connections to existing software. Check what the existing system permits before including an integration in the scope.

The related services are custom web design, ecommerce, Shopify web design, and custom tools.

Built to be found, in Google and in AI answers

A site nobody can find is an expensive brochure. So the search work, and the newer AI-search work, are engineered into the build rather than sold back to you later as a mystery you cannot audit. Some of it is mechanical and either present or absent. Some of it is judgment. We will be clear about which is which.

The mechanical parts, the ones that simply exist or do not:

• Structured data, also called schema markup. This is the labeling that tells Google and other engines what your business is, which services you offer, where you work, and when you are open, in a format built for machines. It is invisible to visitors, and its claims must match the readable page.
• Clean sitemaps, canonical tags, and tidy URLs. These tell crawlers which pages matter and keep them from tripping over duplicates and dead ends. We check these files and tags for consistency; the search engine decides what to index.
• Open Graph and social cards. When someone drops your link into a text message, a group chat, or a social post, this is what makes it show a real title, image, and description instead of a bare gray rectangle. A link that previews well invites a click. A link that looks broken gets skipped.

AI search work also considers being present when a customer asks an AI assistant a question instead of typing into a search bar. That work goes by a few names, GEO, AI search, or AIO. Underneath the labels it is fairly grounded. You write pages that state plainly and correctly what is true. You mark them up cleanly so a machine can read and quote them without guessing. You organize the site so related pages support one another instead of competing. None of it is a trick, and we will be honest that no one fully controls what an AI assistant says. What you can do is make your business easy to read, easy to quote, and clearly trustworthy, and that is the work.

We also publish llms.txt where it fits. It is an optional proposal for providing information to agents using a website. It does not grant crawler access or guarantee citations. Google Search ignores these files. The llms.txt guide explains the limits.

Our free tools cover specific tasks, with their limits described on each tool page: an AI visibility checker, an AIO readiness scanner, a local schema generator, and an llms.txt generator. The deeper explanations live under SEO, local SEO, AI search, and content marketing, and if the map pack matters to your trade, so do your Google Business Profile and your reviews.

Checked before it ships

Our current build requirements include browser, accessibility, and performance checks before release. The evidence records what was checked and what remains unresolved.

• Behavior and forms. Exercise the page's links, buttons, forms, and interactive states in a browser, and inspect console errors.
• Phone and desktop use. Check the layout at phone and desktop widths and use Mobile Safari for the mobile behaviors that need it.
• Accessibility. Run automated accessibility checks and inspect keyboard paths, text contrast, and touch targets. A test result describes the checks performed; it is not a legal certification.
• Performance. Use browser performance traces and Core Web Vitals measurements to identify loading and response issues.
• Forms and sensitive configuration. Keep secrets out of public assets, check form handling and bot protection, and record anything unresolved.

If you already have a website, our free website report card provides a starting point for a review. Ongoing development work is described under web development.

What this means if you run a local business

Here is the plain version, because a page this long owes you one. You do not need most of what is listed above. A strong local website is often a fast, clear set of pages, honest content, clean search markup, and an easy way for the phone to ring. That is the whole job for a lot of businesses, and we are glad to build exactly that. The rest of the toolbox exists for the day you need a store, a booking flow, an estimator, a customer portal, or a custom tool, so that when you grow you are adding to your site instead of starting over with a new agency. If the store you add is on Shopify, how long a Shopify store takes to build has a separate answer.

A few things we hold to no matter the size of the project:

• You own everything. The site, the content, the domain, and the analytics accounts are yours, registered to you and not to us. If you ever decide to leave, you take all of it, and we help you move it cleanly.
• Month to month. No long-term contract. We keep your business by continuing to earn it, which is a healthier arrangement for both of us than a lock-in that lets the work go stale.
• We do not fabricate. No fake reviews, no invented credentials, no statistics we cannot support. We check claims against the approved facts and available sources, and flag anything still unknown before publication. That protects your reputation, and, honestly, it protects ours too.

On cost, we publish real ranges instead of making you ask. Custom website builds run $3,500 to $12,000 and up, one time, depending on how much site there is to build. Ongoing SEO or Local SEO runs $1,500 to $3,500 a month for most businesses, and $3,500 to $7,500 a month in competitive metros or for multiple locations. Custom tools are quoted by scope. The published product menu lists starting prices by tool; back-office systems get a written quote. For Google Ads there is no set management fee, because the honest answer depends on your budget: it is usually billed as a flat monthly amount or as a percentage of ad spend, and we quote a flat number after a free consult so you are not guessing. The full breakdowns live in our guides on what a website costs and what SEO costs, the timelines are covered in how long a build takes and how long SEO takes, and you can explore the pricing tool at what should you pay.

If you would rather see the work than read about it, the simplest start costs nothing: a free mockup of your own site, built the way this page describes, so you can judge the quality before you spend a dollar. Or just ask for a quote, call (407) 694-2055, or send a text. We are based in Orlando, and we have built for local service businesses nationwide since 2008.