Website Design and Online Stores for SMBs

Websites & Ecommerce at Devodin is web design and online store development. Each site is planned around what a visitor came to do, built mobile first, and handed over with the domain, hosting and code in the owner's name. Pages are checked against Core Web Vitals before launch.

How long does a website or online store take to build?

A site typically takes three to six weeks start to finish. A store takes six to ten, because a store adds a product catalog, a payment gateway and a checkout flow that all have to be tested before anything goes live.

The variable that moves the date is rarely code. It is content: photography, product copy, and how quickly you can approve a page once it is in front of you. A landscaping company with one contact form and a photo gallery is a different build than a boutique launching two hundred SKUs before a holiday weekend. Both fit inside the ranges above, but the boutique needs its supplier images, sizing charts and shipping rules ready before the middle weeks start, or the schedule slips on waiting, not on building. Devodin gives a firm date once the scope is signed off, and says so early if anything moves it, instead of a vague estimate nobody can plan a launch around. A companion post covers what determines how long a build takes in more detail.

What happens before a single screen gets designed?

Week one is discovery, not design. Devodin works out which pages the site needs, what each page has to do, who is using it and on what device, then writes that list down before anything gets drawn. That written scope is what both sides refer back to later.

The written scope keeps a project from quietly growing three weeks in, one small addition at a time, until nobody remembers agreeing to any of them. This is where a booking form for a dentist's office and a repair request for a roofer get built as different things, even though both look like a form field on a wireframe. One needs a calendar synced to the live schedule. The other needs a photo upload so a homeowner can send a picture of the damage before anyone drives out. Getting that distinction wrong in week one is expensive to fix in week four. Layouts are agreed in Figma before any code is written, so a change of mind costs a comment, not a rebuild.

What does your site do in the first five seconds on a phone?

The headline has to say what you do, the phone number has to be tappable without hunting for it, and the page has to load before the visitor gives up and taps back to the search results. Many visitors arrive on a phone, standing in a parking lot or on a job site, deciding in seconds whether to call.

Devodin designs and builds mobile first, then tests on phones, not a resized browser window on a monitor. Pages are checked in Lighthouse and against Core Web Vitals, Google's measures of loading speed, responsiveness and layout stability, before launch.

Content management is set up in the same stage, on WordPress where a content-managed site fits, so you can fix a typo or swap a photo yourself, without a phone call to a developer. A roofing company that wants to post "storm response, same-day estimates" the morning after a hailstorm should be able to do it before lunch, not wait for a request to clear someone's inbox.

What is different about building a store instead of a site?

A store adds a product catalog, a payment gateway and a checkout that has to survive money changing hands, tested end to end before launch, not assumed to work because a sandbox transaction went through once. A broken checkout fails silently, at the exact moment a customer was ready to pay.

A broken checkout is the single most expensive bug a store can ship. A store selling one product in four sizes has a structurally different problem than one selling four hundred SKUs across a dozen categories: the first needs a simple, fast path from product to cart, the second needs filtering, search and a catalog structure that search engines can crawl. Devodin builds stores on Shopify or WooCommerce and connects payments through Stripe, PayPal or Square, whichever fits the catalog and how the business already takes money. Both get product pages built to be found, not just to look right on the page, because a product nobody can search for is a product that never sells.

How does a store take an order without friction?

A checkout that asks for too much, or breaks on a phone, is a sale that never finishes. Devodin builds carts and checkouts that get a customer from product page to confirmed order in as few taps as possible, tested end to end with live payment methods before launch.

A single sandbox transaction going through once proves little. That testing happens before the first busy weekend, not after it. A checkout that fails silently on a Friday night, in the middle of a sale, loses a store sales nobody ever hears about, because the customer just closes the tab and buys somewhere else. Devodin stress-tests the order flow, the payment gateway and the confirmation email before a single customer ever reaches them.

What do you own the day the site launches?

The domain, the hosting account, the code repository and the analytics property are registered in your name at launch, not Devodin's. That is what handover means: every login, every file and every account is transferred to you before the project is called finished, with nothing held back.

Leaving Devodin afterward, if you ever wanted to, takes nothing but a conversation, because nothing of yours is still locked to an account you don't control. One team builds the design, the store, the content structure and the search foundation together, so nothing gets handed between departments that quietly forget what the last one built. A named person at Devodin answers when something needs fixing, instead of a support queue that starts over with a stranger every time.

What do launch day and the month after look like?

Launch includes a short support window while you get used to running the site yourself. After that, hosting, backups and security patching move onto an ongoing care plan, if you want one, so the site keeps working the way it did on day one.

Without a plan the site can quietly fall behind. A site nobody patches is a site that eventually breaks in a way nobody notices until a customer does: a broken contact form, a checkout that silently stopped taking a payment method, an update nobody applied. The month after launch is when most of that gets caught, on a plan sized to the workload a business site generates, not built to be forgotten the moment it's set up.

What does website maintenance and a care plan cover?

Website maintenance is the ongoing work that keeps a site running the way it did on launch day. Devodin's Care Plan covers hosting, backups and security patching, uptime and performance checks on a set schedule, and a named person to call when something breaks. The Investment section further down this page shows the monthly cost.

It is optional, and it exists because a site left alone falls behind in small ways: an update nobody applied, a backup nobody tested, a slowdown nobody measured. The plan moves those checks onto a schedule instead of leaving them to whoever remembers.

How does the site get found once it launches?

Analytics and conversion tracking go live at launch, not weeks later once someone remembers to ask for it, so there is a baseline from day one. Pages are also structured to be found: headings in order, descriptive titles, alt text on every image, the plumbing a search engine or an AI answer needs to understand what a page is about.

Together these remove the gap where nobody knows what visitors did before the numbers started. That plumbing is not the same as ranking, which is a longer, separate project covered under search and content. It is the foundation that project builds on. A site launched without it has to be partly rebuilt before search work can even start, which is worth avoiding by getting it right the first time.

Is this the right fit for your business?

This fits a business that needs a site or store that converts visitors, and that wants to own every part of it afterward. It is not the right fit for a project that needs custom software engineered from scratch, which carries a different kind of risk and a different kind of build.

A companion post covers whether your business needs a website at all before you commit to building one. If the goal is a site your customers can use, and one you can keep, this is built for that.

See how a project runs, from first email to handover, read the answers on build timelines, ownership and payment, or browse the articles on websites and positioning.