# Web development > We build the interfaces agent work needs: approval queues, run review screens and internal tools, plus public sites and conversion focused storefronts. Canonical page: https://aispeedforce.com/services/web-development/ Last updated: 2026-08-23 This is supporting work, and it sits under the agent work rather than beside it. We build the interfaces an agent needs a person to use, and the sites and storefronts that sit around it. ## What the web work is for here An agent that writes to a live system needs somewhere a person can see the write, approve it, and read back what happened. That screen is web development. Most of what we build on this line is exactly that. - **approval queues**: The interface where a person clears what an agent wants to write. This is the most common thing we build. - **run review**: A screen that shows a run's plan, tool calls, inputs, outputs and cost, so a trace is readable by someone who did not build the agent. - **internal tools**: The small interfaces a team needs to operate an agent day to day, like editing the rules a guardrail checks against or re-running a job that failed. - **public sites**: Marketing sites and landing pages, built the way this one is: static, accessible, and without a framework unless the work earns one. If the agent itself is the thing you need, that is [agent engineering](https://aispeedforce.com/services/agent-engineering/). This page is the front end around it. ## How we build The same rules on a landing page and on an approval queue. This site is built to them, which is the one claim on this page you can check without asking us for anything. **Semantic HTML**: Real landmarks, headings in order, form controls with labels attached to them. A screen reader and a crawler get the same structure the eye does, because there is only one structure. **One token layer**: Color, type, spacing and motion are defined once as design tokens, and every component reads from them. Nothing is styled inline, so a change lands everywhere at the same time. **Accessible by default**: Visible focus on everything reachable by keyboard, WCAG AA contrast on text, and reduced motion respected. This is part of the build, not a pass we do at the end. **No framework by default**: Responsive from 320 pixels up, and no JavaScript framework unless the work genuinely needs one. When it does need one, we say why before we reach for it. ## Storefront design and development Conversion focused storefronts on the commerce platforms we work on, built inside each platform's own theme and template system rather than bolted on beside it. Storefront work used to have its own page here. It lives in this section now. **Theme and template work**: We work in the theme layer the platform gives us, so the store keeps its admin, its apps and its update path. Templates stay editable by the people who run the shop. **Product and checkout flows**: Collection, product and cart pages laid out around the decision a buyer is actually making, and a checkout path with nothing in it that does not help them finish. **Surfaces an agent can reach**: Where an agent is part of the picture, the storefront exposes the records it needs to read and write, and the queue where a person signs off the writes that matter. ### Platforms we build storefronts on Each platform page covers the agent work as well as the storefront work. - [All platforms](https://aispeedforce.com/platforms/) - [Shopify](https://aispeedforce.com/platforms/shopify/) - [Wix](https://aispeedforce.com/platforms/wix/) - [WordPress](https://aispeedforce.com/platforms/wordpress/) - [Ecwid](https://aispeedforce.com/platforms/ecwid/) - [HighLevel](https://aispeedforce.com/platforms/highlevel/) - [BigCommerce](https://aispeedforce.com/platforms/bigcommerce/) Once a store is live, ranking it is a separate job. That is [SEO](https://aispeedforce.com/services/seo/). The full picture is on [what we build](https://aispeedforce.com/services/). ## Questions we get asked first ### Do you take on website work on its own, without an agent project? Yes. Sites, landing pages and storefronts are work we take standalone, and we will say plainly when a job has no agent in it and does not need one. What does not change is how it gets built: semantic HTML, accessible by default, and a framework only where the work asks for one. ### What do you build with? Semantic HTML, CSS driven by a single design token layer, and JavaScript only where it earns its place. On platform work we build inside the platform's own theme and template system rather than bolting a separate front end on top. This site is built that way, which is a claim you can check by reading its source. ### Do we own the code? You do. Code goes into a repository you control and deploys to hosting in your name. Nothing we write is held behind a license you have to keep paying us for, and you keep it whether or not we keep working together. ## Tell us what the screen has to do A queue someone clears every morning, a store that has to sell, or a site that has to load. Describe the job and we will tell you what it takes to build and whether an agent belongs behind it.