From the first call through launch and the support that follows.
Every build follows the same path. The size of the project changes the schedule, not the steps. Here is how a typical project with Sitebix Services runs.
We start with a conversation about the site or app you need, who it is for, and what is already in place. You can share a current URL, a rough list of pages, or just the problem you want solved. We ask about timeline, budget range, and who will look after the site once it is live. The call is usually 30 to 45 minutes. If a written note is easier, the Start a project form covers the same ground.
After the call we send a written proposal. It names the work, what is in scope, what is out of scope, and a quote for that scope. We do not publish package prices, because the real build depends on pages, features, and content. You can accept the quote, ask for a smaller first phase, or walk away. We do not start design or build until you approve the quote in writing.
We turn the approved scope into a sitemap and a simple wireframe. The sitemap lists the pages and how people move between them. The wireframe shows layout and content blocks without final colors or type. You review this before visual design, so a change to the structure stays small.
We design the key screens in navy and blue, or in your brand colors if you already have them. You review a small set of pages first, usually the home page and one inner page. Once those are approved, we apply the same system to the rest. Design notes stay in the shared project document so comments live in one place.
We build the approved design in the stack named in the quote. Most marketing sites are WordPress. Stores, portals, and custom apps use the stack that fits the job. You see working pages as they are ready, not only a big reveal at the end. The code lives in a repository, and you can have access to it.
Words, photos, and product data can come from you, or we can help shape them. The quote says which. If you are writing the pages, we give you a simple content list with the fields each page needs. Placeholder copy is marked so it does not ship by accident. Logos and brand files should be vectors or large PNG files.
Before launch we click through the real paths: forms, checkout, login, and the pages on your sitemap. We check the site on a phone and a desktop browser, and we run the accessibility checks described on our Accessibility page. You get a short list of what we tested and anything still open. We fix defects that are in the agreed scope before go-live.
We agree a launch window. We point the domain, turn on HTTPS, set redirects from old URLs when you have them, and submit the sitemap. We watch the live site for the first day and fix anything that only shows up in production. You approve the launch checklist before we call it done.
After launch we walk you through the tasks you will actually do: edit a page, add a post, check a form, or update a product. The walkthrough is a video call, and we leave short written notes. You receive admin access, where the code lives, and who to email if something breaks.
If you want us to stay, the Care Plan covers updates, backups, a watch on uptime, and small fixes from the people who built the site. Larger changes are quoted as new work. If you take the site in-house, the handoff still includes what you need to run it without us.
These are typical ranges, not a promise. The quote states the schedule for your project.
Delays usually come from late content, extra pages, or a change in scope. We reset the date in writing when that happens.
We do not require a specific chat tool. If your team already uses one, we can work there.
The quote includes a set number of review rounds for design and for the built site. A round is one set of comments and one revision. Small text fixes during a round are part of that round. New pages, new features, or a new direction after approval are extra scope. We quote that before we build it, so the schedule and the price stay clear.
No. A sentence about the business and the problem is enough. The call is how we fill in the rest.
Yes. Many projects start as a Presence or Business site and add a store, a portal, or a care plan later.
You can, or we can. The quote says which. If you write them, we still edit structure, headings, and links so the pages are usable.
Tell us as soon as you know. We can pause or move the window. We confirm the new date in writing.
Yes. A redesign, a WordPress rescue, or a maintenance plan can start from the site you already have. Say so on the project form.
We operate in Fort Lauderdale, FL and Jamaica, and we serve the US and the Caribbean. Projects run remotely. Video calls cover the reviews.