Questions
The things people always ask.
If your question is not here, email it and we will answer it properly — and add it to this page.
- Answered plainly
- Updated as questions arrive
- Ask anything that is missing
A focused landing page can go live in about two weeks. A full business website usually runs three to six weeks. Automation and AI work is layered on afterwards in two to four week blocks, so you get value before the whole system is finished.
There are no fixed packages. We scope against what you are trying to achieve, then give you a written proposal with a fixed price and timeline before anything starts. The pricing page has indicative ranges.
Yes — Startup Launch exists for exactly that. We take a rough idea through positioning, brand, website, launch and the first marketing push, then automate the parts that repeat.
Yes. Code, designs, domains, accounts and automations are yours. We hand over full ownership on final payment — no hostage hosting, no locked platforms.
Usually. We start with an audit of the current build, tell you honestly whether it is worth improving or rebuilding, and give you the numbers behind that recommendation rather than a sales pitch.
Launch is the middle of the project, not the end. Hosting, monitoring, iteration, marketing and automation continue through your dashboard, and you can scale that support up or down whenever you need to.
Dropshipping means selling products your supplier ships directly to the customer, so you never hold stock. We set up the storefront, import products, wire payments and fulfilment, and launch the first campaigns. There is a clickable demo of the whole flow on the homepage.
Yes. We build agents trained on your own documentation and product data. They answer first-line questions in your tone of voice, work around the clock, and hand over to a human whenever a conversation needs one.
We pick the platform to fit the job: Next.js and static builds for marketing sites and web apps, Shopify or WooCommerce for stores, custom stacks for software. You are never locked into a proprietary builder.
Yes. AWGCOR works with clients worldwide and runs asynchronously through the dashboard, so time zones are not a blocker. Most communication is in writing, with weekly demos.
Every proposal states the number of included rounds. A round means one consolidated set of feedback rather than an open stream of individual changes. Extra rounds are quoted before they start.
Then a good freelancer is probably a better fit, and we will tell you that on the call rather than after the invoice. We are built for businesses that need several things working together.
- Who will I actually be dealing with?
- One named person who is also involved in building the thing. No account manager relaying messages to someone you never meet.
- How often will I hear from you?
- A written update once a week, plus whenever something needs a decision. You can also watch progress in the dashboard whenever you like.
- What do you need from me?
- Roughly two hours in the first week for the brief and account access, then about thirty minutes a week for review. Content and approvals are the only things that reliably slow projects down.
- What if I go quiet for a few weeks?
- The project pauses and nothing expires. Timelines shift by however long the pause was; nobody re-prices it.
- Why no published price list?
- Because the same word covers wildly different jobs. We publish the method and indicative ranges on the pricing page and then price your actual scope.
- When do I pay?
- Usually a deposit to start and the balance on handover. Longer builds split into three milestones.
- Are there ongoing costs?
- Only ones you choose. Hosting sits in your own account and is typically a few dollars a month. Support and marketing are optional and month to month.
- What if the price turns out to be wrong?
- Then it is our problem, not yours. The fixed price is fixed; it moves only if you ask for something that was not on the list, and that gets priced before it starts.
- What do you build with?
- Static sites are hand-written HTML, CSS and JavaScript with no runtime dependencies. Applications use whatever genuinely fits — commonly Next.js, Node, Postgres and Stripe. Stores are Shopify or WooCommerce.
- Can my own developer maintain it?
- Yes, and that is a design goal rather than a side effect. No proprietary builder, no format only we can open.
- Where will it be hosted?
- Wherever you want, in your account. cPanel, Vercel, Cloudflare and traditional VPS hosting are all fine — a static site has no special requirements.
- What about accessibility?
- Real headings, real labels, keyboard reachable, visible focus and respect for reduced-motion settings. It is part of the build, not a line item.
- Do I own the code?
- Yes — all of it, in a repository in your name, with history.
- Do I own the accounts?
- Yes. Domain, hosting, ad accounts, analytics and any third-party service are created in your name or transferred to it.
- What if we stop working together?
- You keep everything and owe nothing. There is no exit fee and no notice period, and you can request handover at any point, including halfway through a project.
- Will you keep working on it afterwards?
- If you want us to. If you would rather take it in-house, the handover document is written for exactly that.
Ready when you are.
Tell us what you're building and we'll map the shortest route there.