FAQs

Question 1

Who owns the website when the project is over?

Accepted Answer

You do, and that includes every piece of it, the source code on GitHub that gets trasferred to your GitHub account at the handoff, the design assets created on the design and development step (backgrounds, PNGs, shapes, patterns, etc), the domain (initially provided by you or we help you to get one), the hosting, the database, the database backups, and storage accounts. None of it sits behind a Cromática login, we give you all of credentials of all of the accounts needed to build your site. This is not a courtesy extended at the end of a project that went well. It is how the project is set up on day one, the accounts are created in your name before a single line of code is written, so there is never a moment where handing things over is something we have to agree to.

Question 2

Do you provide the domain, or do I?

Accepted Answer

You buy it, and it is deliberately left out of the quote. A domain is not something we produce for you, it is the piece of your brand that will outlive every website you ever have, including this one. It belongs on your card and in your name from day one, rather than being transferred to you later as a favor. If you do not have one yet, that is not an obstacle. We help you pick a name, check what is available, and register it on the best domain platforms nowadays, like Namecheap, Cloudflare Domains, Spaceship and GoDaddy, every one of those works. You pay the register directly, usually somewhere between $10 and $20 a year depending on the extension. We do not resell domains and we take no margin on them.

Question 3

How is the source code transferred to me?

Accepted Answer

Through GitHub, once the project is handed off and completely done, this is one of the last steps of our process lifecycle. If you already have a GitHub account or organization, the repository gets trasferred to your account. If maintenance is needed later, and you would like to do it with us, you give the access to our developers to the repository, as collaborators. Works the same if we need to improve some config files on the storage or database. When the project ends we simply step out. If you do not have an account, creating one takes a few minutes and costs nothing, private repositories are free. We walk you through it at the moment of the transfer. GitHub's transfer keeps the full commit history, the issues and the settings intact. If you would rather not use GitHub at all, that works too. You receive the complete repository with its entire history as an archive you can push to GitLab, Bitbucket or your own server. Whichever route you take, we keep access afterwards only if you have a maintenance agreement with us. Otherwise our access goes away along with everything else.

Question 4

What exactly do I receive at handoff?

Accepted Answer

Five things, the live site running on your chosen hosting, the repository (source code) with its full commit history, the design files produced during the design and development steps, documentation that walks you through how to get the most value out of our site and the accounts needed for your site to be live, like the hosting, the media storage and database accounts.

Question 5

Who owns the design files and the content?

Accepted Answer

Yours. That covers the design files, the layouts, every asset we used on the page like the images, backgrounds, PNGs, patterns, shapes or anything else produced for the project. This is easier to promise than it sounds, because the design is not a template we licensed and adapted. It was designed for your site, which means there is no third party whose terms limit what you can do with it, and no other client out there running the same design.

Question 6

What happens to my site if Cromática stops operating?

Accepted Answer

It keeps running. The site is hosted on your preferred hosting platform, the domain renews on your card, the database and the files sit under your billing, and the repository is already in your hands. Nothing in that chain depends on Cromática continuing to exist. That is the practical reason the account policy matters, and it is worth asking of any agency you talk to.

Question 7

What time zone do you work in? Will our hours overlap?

Accepted Answer

We are in Lima, Peru, on UTC-5 all year, because Peru does not observe daylight saving time. From November through March we are on the same clock as New York, from March through November we are one hour behind it. Against the West Coast the gap runs two to three hours depending on the season. At no point in the year are we more than three hours from anywhere in the continental United States. In practice that means you can send a message in the morning and have an answer before lunch, and that scheduling a call never requires anyone to take it at an uncomfortable hour. It is the quiet reason working with us feels closer to hiring someone two states over than hiring offshore.

Question 8

Who will I actually be working with?

Accepted Answer

The person building your site. You talk to them directly every time you need to, in English or Spanish, from the first call through to the handoff. There is no account manager in between relaying your feedback, and nobody disappears once the contract is signed to be replaced by someone you never met. That is a deliberate limit on how much work we take on, not an accident of being small. A message about a layout detail reaches the person who wrote that layout, which is why answers come back in hours rather than days, and why nothing is lost in translation between sales and production.

Question 9

How often will I hear from you, and through what channel?

Accepted Answer

You get a written update once a week if you would like to, whether or not there is dramatic news. Silence is the most common complaint about remote work and it is almost always avoidable. On top of that you have a live preview link from early on, so you can look at the actual site whenever you feel like it instead of waiting to be shown it. Email is the main channel, and it is where the record of every decision lives. Calls happen at the boundaries of each stage, when something needs deciding rather than describing but we can arrange one at any time you want. For smaller questions in between, you can write on any working day and get an answer the same day.

Question 10

What do you need from me before we can start?

Accepted Answer

Your brand files, like your logotype and isotype. Your used fonts on other projects for your branding, your color palette. An email account of your organization to use it for every service the project will require, like the storage bucket on cloudflare for the media, like images, videos or docs, or the database account on postgres platforms like Neon, or the deployment on vercel. If you don't want to create one, we can create one for you and hand it over at the end of the project without problems. And we also need one person on your side with the authority to approve decisions, this saves a lot of time. The last one matters more than it sounds. The most common cause of a delayed project is not missing content, it's feedback arriving from three people who disagree with each other. One decision-maker, with whoever else they want to consult standing behind them, is what keeps a four-week project from turning into a four-month one. If you do not have all of it, that is normal and not a blocker. We tell you exactly what is missing before quoting, so nothing surfaces halfway through as a surprise.

Question 11

Do you sign contracts and NDAs?

Accepted Answer

Yes. No project starts on a handshake. Before any work begins there is a written agreement setting out the scope, the final price, the timeline and who owns what at the end, not because we distrust anyone, but because that document is what you hold us to if something goes wrong. The agreement and the invoicing both run through the contracting platform we work on. That means the paperwork is standardized rather than improvised, and you receive a proper invoice you can file with your accounting. If your company has its own NDA or contractor agreement, send it over and we review and sign it. That is common with larger clients and it has never been a problem.

Question 12

Can I edit the content myself, without calling you?

Accepted Answer

Yes, and not the stripped-down version of editing that some agencies hand over. Your site comes with an admin panel where you change text and images on any page, reorder sections, hide a section you are not using without deleting what is inside it, and publish new pages built from the same sections the rest of the site uses. None of that requires code or a developer. If you can fill in a form, you can run your site. The pieces that would be dangerous to break, the layout rules, the styling, the structure, are the ones we keep out of your way on purpose, so there is no version of this where you were editing a page and the site went down. Changes go live when you publish them, not when we get around to it.

Question 13

What is the site built with, and why should I care?

Accepted Answer

Next.js for the site itself, Payload as the content manager, and PostgreSQL for the database. All three are open source, widely used, and documented in public. The reason that matters to you has nothing to do with engineering taste. There is no proprietary Cromática framework, no licensed page builder, and no monthly fee to a platform that could change its pricing or shut down. If you ever want to work with someone else, they will recognize what they are looking at on the first day. Replacing us is a hiring problem, not a technical one. It is also why your site is not a WordPress install held together by fifteen plugins. Fewer moving parts from third parties means fewer things that break on someone else's schedule instead of yours.

Question 14

Can the site be in two languages? Who writes the translations?

Accepted Answer

Yes. On average, most clients take two languages, and they are part of how the site is built, not a plugin added later. Every piece of text, headings, buttons, page titles, the words search engines read, has its own field for each language, which means both versions are genuinely yours to control, editable, word by word. That matters more than it sounds. The common shortcut is an automatic translation widget that rewrites the page in the visitor's browser. Search engines do not index those versions, so your Spanish-speaking customers never find you by searching in Spanish, which was the entire point of having a second language. On who writes them: you can supply both languages, or we write the second one as part of the project. Either way the text is yours to edit afterwards from the same admin panel.

Question 15

Can you connect it to my CRM, calendar, newsletter or analytics?

Accepted Answer

Usually, yes. Booking and scheduling, contact forms that drop straight into your CRM, newsletter signups, analytics, these are the common ones and they are routine work. Beyond those, the honest answer is that almost anything with a public API can be connected. What changes is how much work it takes, which is why integrations get scoped at the start rather than promised in the abstract. Tell us what you already use during the requirements stage and you get a straight answer before committing to anything. What we will not do is connect something badly in order to tick a box. If a tool's API cannot do what you actually need, we say so, rather than building a half-working bridge you discover is broken three months later.

Question 16

Will my site be fast, and will it show up on Google?

Accepted Answer

Speed is a consequence of how the site is built, not something optimized at the end. Pages are generated ahead of time and served ready-made, so a visitor is not waiting on a database query and a dozen plugins before anything appears. Images are compressed and sized for the device asking for them. On search, a site can be built to be found or built to get in the way, and that part is on us. Clean page structure, real headings, titles and descriptions you control per page and per language, a sitemap, and pages that render without JavaScript having to run first. That is the groundwork, and it goes into every project. What we will not promise is a position on Google. Ranking depends on your competition, your industry and what you publish over time, none of which a developer controls. Anyone who guarantees you a first page is selling you something they cannot deliver.

Question 17

What if I need a feature in the future?

Accepted Answer

It gets built as a new section and dropped into the site. Your pages are assembled from independent blocks, a hero (first block in page, like a 'header'), a pricing table, a gallery, a form, and a new capability becomes a new block that sits alongside the ones already there. The practical consequence is that growing does not mean starting over. Adding a blog, a booking flow or a product catalogue a year from now is work on top of what exists, not a second project that throws away the first. It is also why starting on a smaller tier is not a trap: you are not buying a lesser site that has to be replaced once you outgrow it. If what you need is big enough to require real planning, we say so up front with a scope and a number, the same way as the original project.

Question 18

What are the steps, from the first call to launch?

Accepted Answer

Four stages, each ending with something concrete you look at and approve before the next one starts. Nothing moves forward on an assumption, and you are never more than one stage away from the last thing you signed off on. Requirements comes first, and it is about the business before the website: what you sell, who buys it, what you want a visitor to do when they land, and what is working or failing today. It is also where the scope gets written down, like how many pages, which sections, which integrations, which languages. Everything after this refers back to what was agreed here, which is why it is the one stage worth being slow about. Design comes next. You see the actual pages, layout, typography, color, how the thing behaves on a phone, before a single line of production code is written. This is the cheapest point in the whole project to change your mind, and we would rather you use it. Approving the design is what unlocks development. Development turns the approved design into the working site, the pages, the content management panel, the forms, the integrations, the second language. You have a live preview link throughout this stage, so you are watching it come together…

Question 19

How long does a project take?

Accepted Answer

It depends on size. A single landing page runs from about 7 to 14 days. A multi-section site is usually around 15 to 30 days. A larger build means more pages, a blog, a catalogue, several integrations, lands between 30 to 45 days. You get the exact time for your project in writing before anything starts, as part of the agreement. Those are working days on our side, and they assume one thing that matters enormously, the clock starts when your material is in our hands, not when you pay. If the copy, the logo and the photographs arrive two weeks after the deposit, the project finishes two weeks later. Inside that window the stages are not evenly sized. Requirements and design take a larger share than most people expect, and development is faster than they expect, because by the time it starts every decision has already been made. A project that moves deliberately at the beginning tends to finish early; one that rushes the beginning finishes late, every time. And if we see a date starting to slip, you hear it from us the moment we see it, not on the day it was due.

Question 20

How many rounds of revisions do I get, and what counts as one?

Accepted Answer

The revision rounds normally takes place when the design stage is done and we're about to start building. On growth, where you get two rounds, one when the design is done and another when the site is built. And finally on scale, one when the design is done, another when the site is built, and the last one when the deployment has all the optimizations we add, like the deployment or assets optimizations. But some exceptions can take place, either way the exact number is written into your agreement, so it is never something to argue about later. What counts as a round matters more than the count itself. A round is all of your feedback, gathered and sent at once. Ten comments in a single message is one round. Three messages over three days with one comment each is three rounds, and that is not a technicality, it is the honest cost. Every time we stop, change one thing and start again, the project loses time, more than the change itself takes. So the practical advice, which saves you rounds and saves everyone time, sit with the design for a day, write down everything that bothers you or could look/work better, and send it in one piece. If several people on your side have opinions,…

Question 21

What if I don't like the design?

Accepted Answer

If we're in the design stage, we change it. That is the entire purpose of having a design stage, to see the real pages before any production code exists. If you realize that we need to change direction on the design or features of your project, could mean extra costs. There is a difference worth naming between not liking a detail and not liking the direction. A detail, the color of a button, a headline that reads wrong, two sections in the wrong order,is a revision, and it gets handled in the next pass. A direction, the whole thing feels corporate when you wanted warm, or restrained when you wanted bold, is a bigger conversation, and it usually means something was missed back in requirements. When that happens we go back there instead of patching forward, because patching forward is how a design ends up as a compromise nobody chose. This is also why the design is shown before anything is built rather than after. An agency that hands you a finished website and then asks what you think has arranged matters so that your honest answer is expensive. We would rather find out early, when it is cheap, even though it means hearing criticism sooner. In the rare case where we cannot find a…

Question 22

What do I need to approve, and when?

Accepted Answer

Before any of it comes the scope. Every project, on every tier, starts with a written description of what is being built, the pages, the sections, the integrations, the languages, the price and the timeline, agreed before work begins. Everything below refers back to that document. From there, how many times the project formally waits on you depends on the tier you chose. On Launch there is one revision: the design, at the end of the design stage. You are approving how the site looks and behaves, and development is built against exactly what you approved. Being a single gate, it deserves a careful look rather than a quick one. On Growth there are two: the design, and then the finished build before it goes live. The second is where you confirm that what was built matches what was approved, that the content reads correctly, and that nothing is missing. On Scale there are three: the design, the build, and the deployment where you sign off on the performance and configuration work done at launch, not only on how the site looks. Each of those is a specific decision with a yes or a no attached, not an open-ended review. We tell you what we need and by when, and if you need longer, say…

Question 23

What could delay the project?

Accepted Answer

In practice, almost never the code. Three things account for nearly every delayed project, and all three sit on the client's side, which is not an accusation, just something worth knowing in advance. Content arriving late is the most common by a wide margin. Copy, photographs, logos, product details. A site cannot be finished with placeholder text, and the week spent waiting for the last three paragraphs is a week nobody planned for. If writing the copy is the part you are dreading, say so at the start and we handle it differently rather than letting it quietly become the bottleneck. Feedback from several people who disagree is the second. Four stakeholders sending contradictory notes does not produce a better site; it produces a slower one, and usually a more timid one, because the design drifts toward whatever offends nobody. This is why we ask for one person with the authority to decide, with whoever else they want to consult standing behind them. A decision nobody is empowered to make is the third, and the quietest of the three. The project stops, nobody notices for a week, and a stage boundary passes with nothing moving. We raise these the moment we hit one rather than…

Question 24

What happens after the site goes live? Is there a warranty?

Accepted Answer

The post sale support window depends on your tier, fifteen days on Launch, thirty on Growth, sixty on Scale. Inside it, anything that does not work the way it was approved gets fixed at no cost. Not a credit, not a discount on a future invoice, fixed, however long it takes us. That covers the site doing something other than what was agreed, a form that stops delivering, a page that breaks on a phone, a layout that falls apart in a browser we said we supported, a translation field that will not save. If it was supposed to work and it does not, it is ours. What it does not cover is new work. Adding a section, reversing a design decision you approved, connecting a tool that was never in the scope, those are changes. The next question explains exactly where that line sits, because the distinction causes more friction after launch than anything else. Nothing expires in a way that leaves you stranded. Once the window closes the site keeps running exactly as it was. The warranty ending means our obligation to fix things for free ends, not that the site needs us in order to keep working. From there you can take out a maintenance plan, come back for individual pieces of work, or run it…

Question 25

What counts as a bug, and what counts as a new feature?

Accepted Answer

A bug is the site failing to do what was agreed and approved. A change is the site doing something it was never asked, mentioned or approved. Everything after launch falls into one of those two. Bugs look like this: the contact form stops sending. A page renders wrong on a phone. The Spanish version of a heading will not save. A link goes nowhere. An image gallery stops loading. None of those cost you anything during the warranty, because the site is not doing what you approved. Changes look like this, adding a new testimonials section. Connecting a newsletter tool that was not in the original scope. Adding a third language. Restructuring the navigation. These are new work, not because we are being strict, but because they were not part of what was agreed and priced. The honest grey area is a design decision you approved and have since cooled on. The header you signed off in week two feels wrong by month two. That is a change, and a completely normal one, most sites get a few. One rule cuts through most of the arguments: if we misread the requirements or built something other than what was approved, it is a bug, however much it looks like a feature request. Our mistakes stay ours.

Question 26

How fast do you respond if something breaks?

Accepted Answer

You get a first reply within one business day, always, including the kind of reply that says we have seen it and here is what we are checking. Not knowing whether anyone read your message is worse than waiting for the fix. If the site is down, or something is broken for your customers, a form not delivering, pages not loading, it jumps the queue and we work on it the same day. Something cosmetic, or a question, gets answered within the day and scheduled normally. Being in Peru on UTC-5 helps here more than it sounds. An email sent during your morning on the East Coast is read during our morning, not twelve hours later while you sleep. It also means we are not a 24/7 operation with someone on call at three in the morning, and we would rather say that plainly than imply otherwise and disappoint you exactly once. If something turns out to be harder than it looked, you hear what we found and what we are doing about it rather than silence while we work on it. A problem being difficult is not a reason to stop talking about it, it is the reason to start.

Question 27

Do you offer maintenance? What does it include?

Accepted Answer

Maintenance is an optional plan, and optional means optional, the site does not degrade or stop working without one. Plenty of clients with live sites, run the site themselves for a year, and come back only when they want something new. A plan covers keeping the underlying dependencies and security patches current, checking that the automatic backups are genuinely running and genuinely restorable, monitoring that the site is up, a monthly allowance of small content or layout changes, and priority in the queue when something needs attention. The second item is the one worth paying attention to. Almost every hosting platform takes automatic backups, and almost nobody ever tests whether they restore. A backup that has been failing quietly for four months is indistinguishable from a working one right up until the day you need it, which is the day you find out. Without a plan, nothing bad happens immediately. The site keeps running, the hosting keeps backing up, and you keep full control of everything. What accumulates slowly is the updates, six months of skipped security patches is not an emergency, but two years of them turns a small job into a large one. If you would rather not have…

Question 28

How do I learn to use the admin panel? Is there training?

Accepted Answer

Through a video library rather than a manual. Every feature of the panel has a short explainer video showing the thing actually being done, step by step: changing text, swapping an image, adding a blog post, publishing a new page, hiding a section you are not using for now. They live at cromatica.media/en/docs, they are available at any hour from any device, and they stay there for as long as your site does. Nothing to download, nothing to misplace, no PDF quietly going stale in an inbox from two years ago. You also have access before your site is delivered, not after. That matters more than it sounds. By the time handoff arrives you already know what the panel does, so the handover is a confirmation rather than a lesson, and it means you can see exactly how editing works before committing to anything. Reading instructions and watching someone do the thing are not the same. Almost everyone who watches the two-minute video gets it right the first time. Almost everyone who skims a written list of steps writes to us halfway through. The panel itself is built to make this easy, and that is a deliberate design choice rather than a happy accident. You can change content, reorder…

Question 29

Is my site secure? Who handles updates and backups?

Accepted Answer

The site is served over HTTPS with a certificate that renews itself. The database and the files sits on managed infrastructure that takes automatic backups as part of the service. None of that depends on anyone remembering to do anything, it's already automated. Those backups are yours, because the accounts are in your name. We set them up during handoff and show you where they live and how a restore actually works, so recovering from problem like that can be resolved by you or your team and contacting us is not a must. The gap worth naming out loud is that automatic backups and verified backups are not the same thing. Platforms back up reliably right until the moment they quietly stop, and a backup nobody has ever tested is a guess. Checking that they exist and that they genuinely restore is part of a maintenance plan with us, because doing it requires standing access to your accounts, which we do not keep after handoff unless you have the maintenance plan with us. On security more broadly, there is no public admin login beyond your own, no ecosystem of third-party plugins each carrying its own vulnerabilities, and far fewer moving parts than a typical CMS install. The most…

Question 30

How much does a website cost?

Accepted Answer

Three tiers, and what separates them is how much site you need rather than how well it is made. The care is the same in all three. Launch starts at $400. One page with up to five sections, one language, one contact destination, and the SEO basics every site needs, a sitemap, metadata, structured data. The content dashboard and the video documentation are included from day one, along with fifteen days of post-launch support. It is the right size for one well-made page that does one job. Growth starts at $800. Up to five pages and twenty-five sections, two languages, two contact destinations, dark mode, and the collections that let a site grow without us: a blog and an FAQ section you manage yourself. It adds the SEO schemas for those collections, CRM connection and Google Analytics, and thirty days of support. Scale starts at $1,200. Up to ten pages and forty sections, three languages or more, mega-menu navigation, and dedicated performance work, Core Web Vitals, lazy loading, image compression, measured and tuned after the site is built rather than assumed. Sixty days of support. Every one of those says starts at, and it is literal. Most projects add something: an extra…

Question 31

What is not included in the price?

Accepted Answer

Two things sit outside the quote, and both for the same reason, they are recurring services from other companies, not work we do for you. The first is the domain. You buy it, it stays in your name, and it typically runs between $10 and $20 a year depending on the extension. If you do not have one yet we help you choose and register it. The second is what it costs to keep the site online once it is launched: the deployment platform that serves your pages, the database that holds your content, and the Cloudflare storage service that holds your images and files. These are monthly or usage-based, they scale with how much traffic you get, and for a small business site they are usually modest. We set all three up in your name during the project, configure them, and show you exactly what each one bills, so there is never a surprise charge appearing somewhere you did not know existed. You pay those providers directly. We do not resell infrastructure and we take no margin on it, because the moment your hosting runs through our account, leaving us stops being a decision and becomes a negotiation. Two smaller things also sit outside the price, and they are worth naming: subscriptions to…

Question 32

How and when do I pay?

Accepted Answer

It depends on the size of the project, because the point of splitting a payment is to share risk on something long, and Launch is not long. On Launch, the full amount is paid before development begins. It is the smallest tier and the shortest timeline, and splitting a few hundred dollars into two transfers adds paperwork for both sides without protecting either of us from anything. On Growth and Scale, half at the start and half at delivery. The first half is what puts your project in the calendar and starts the work. The second falls due when the site is finished and approved by you, so you are never paying for something you have not yet seen. The agreement and the invoicing both run through the contracting platform we work on, which means the paperwork is standardized rather than improvised, and you receive a proper invoice you can file with your accounting. One thing that does not change at any point: the price is fixed before work begins. We do not bill by the hour, so if something takes us longer than we estimated, that is our problem to absorb and not a new line on your invoice. The only way the number moves is if you ask for something that was not in the agreed scope, and…

Question 33

How much does maintenance cost?

Accepted Answer

$150 a month, and it is genuinely optional. The site does not degrade or stop working without it, and plenty of clients run on their own for a year and come back only when they want something new. The first thing it buys is that the site stays current. The libraries a site is built on release security patches continuously, and skipping them is not an emergency at six months but turns into a large job at two years. Keeping up is cheap; catching up is not. The second is verified backups, and this is the part most worth paying for. Almost every platform takes automatic backups, and almost nobody ever tests whether they restore. A backup that has been failing quietly for four months is indistinguishable from a working one right up until the day you need it, which is the day you find out. Under a plan, someone actually checks, which requires standing access to your accounts, and that is access we do not keep after handoff unless you have one. The rest is monitoring that the site is up rather than hearing about it from a customer, a monthly allowance of small content or layout changes so that a new phone number or a swapped photo does not need a quote, and priority in the queue when two…

Question 34

Which tier do I need?

Accepted Answer

The useful question is not which tier has more in it. It is what you need your site to do over the next year. Launch is for founders, creators and independent professionals. One page, doing one job well: explaining what you do and making it easy to contact you. If your audience already finds you somewhere else, social media, word of mouth, a client list, and what you lack is a credible place to send them, this is the whole answer. You do not need a blog you are not going to write. Growth is for a small business that wants to be found rather than just referred. The real jump here is SEO, and it is bigger than the feature list makes it look: the collection schemas mean search engines understand what each page is, like an article, a product or a project,instead of only seeing that it contains words. On top of that you get a blog and an FAQ section you grow yourself without calling us, a second language, and the CRM and Analytics connections that let you see which pages are actually bringing people in. This is the tier for a business whose site is supposed to be working while nobody is looking at it. Scale is for a larger company where the site is a channel with revenue attached. You…

Question 35

Do you offer refunds? What if I cancel?

Accepted Answer

Yes, and the amount depends on how far the project has gone, because by then some of the work exists whether or not you want to continue. If we are still in requirements and design has not started, you get everything back. Nothing has been produced yet beyond conversations, and we are not going to charge you for having changed your mind early. This is the cheapest possible moment to walk away and we would far rather you use it than carry on out of politeness. Once the design stage has begun, meaning we have started producing the actual pages you would approve, the refund is 70%. The remaining 30% covers design work that exists, that you keep, and that you are free to take to someone else. Once development has begun, meaning code is being written against an approved design, the refund is 50%. By that point you are holding a design you approved and a partial build, both of which are yours. What a refund is not for is a finished site you have cooled on after launch. Once the project is delivered and approved, the post-launch support covers defects, things not working the way they were approved, and the line between a defect and a change is explained in the support section. Cancelling…

Question 36

Can I upgrade to a higher tier later?

Accepted Answer

Yes. Nothing about a lower tier locks you out of anything later. The things that separate the tiers, a second language, a blog collection, the SEO schemas, mega-menu navigation, the performance work, can all be built and added to a site that is already running. The honest part is what it costs. Each of those becomes its own small project, with its own scoping, its own testing and its own deployment. Inside the original build they share all of that between them; afterwards each one carries it alone. Add three features one at a time over a year and you will have paid noticeably more than the tier that included them would have cost. That is not a penalty we invented to push you upward, it is just how the work divides. One pass over a site that is being built is cheaper than three separate returns to a site that is already live and cannot break. So the practical advice is to choose for the year ahead rather than the month ahead, but accurately, not defensively. If you are genuinely unsure, tell us what you expect to be doing in a year, publishing articles, selling in two languages, running campaigns that drive real traffic, and we will tell you where the line falls. Sometimes that…

Question 37

Why hire you instead of building it myself on Wix or Squarespace?

Accepted Answer

Sometimes you should use one, and we would rather say that than take four hundred dollars from someone who did not need us. If you need a single page, you have a weekend, and the site is closer to a business card than to a channel, a builder will do the job and we are not going to pretend otherwise. What changes when you hire this instead is what you end up owning. On a builder you are renting your site's existence from a company, the pages live in their editor, in their format, on their plan, and they cannot be taken anywhere else. If the pricing changes, your only move is to pay it. Here the code is yours in a standard format that any developer can continue, which is the difference between owning an asset and holding a subscription. The second difference is what search engines can actually see. A drag-and-drop editor produces pages that look right and are structurally vague, generic containers where there should be headings, articles, products. The collection schemas we build tell a search engine what each page is, not merely that it contains words. On a builder that level of structure is either unavailable or sitting behind a plugin and a higher plan. Then there is the part…

Question 38

Why are you cheaper than a US agency?

Accepted Answer

Because our costs are different, not our standards. It is a fair question and one worth asking out loud rather than quietly wondering about, because the usual explanation for a price gap this size is that something is being skipped. We are based in Lima - Peru. The cost of living here is a fraction of what it is in a US city, and that alone accounts for most of the difference. On top of it, most of our team works remotely, no sales team taking a commission on your project, and no account managers sitting between you and the person writing the code. An agency charging eight thousand dollars is often paying half of it to people who never touch your site. The third piece is our own doing. We maintain a component library, the sections, the layouts, the content panel, every pattern we have already solved properly, and each project is assembled from it rather than rebuilding the same contact form for the eleventh time. That is not the same thing as a template, the design is drawn for your site and nobody else runs it. What gets reused is the engineering underneath, which is exactly the part you should not be paying anyone to reinvent. What we do not do is cut the things that stay…

Question 39

How do I get started?

Accepted Answer

Write to us, or book a call. There is nothing you need to prepare first just your need to have a functional and reliable website. You do not need to know which tier you want, you do not need your content written, and you do not need to have thought through what pages you need, working that out is the point of the conversation, not a prerequisite for having it. The message reaches the person who would build your site, not a form that gets triaged by someone else. You get a reply within one business day. The first call runs about thirty minutes and it is about your business rather than about websites. What you sell, who buys it, what you want someone to do when they land on your page, and what is or is not working today. From that we can usually name the tier, the price and the timeline before the call is over. Sometimes the answer is that we are not what you need: the project is larger than what we do, or smaller, or genuinely the job of a different kind of specialist. We will say so on the call rather than quote you anyway and work it out later. A badly matched project is a worse outcome for us than no project at all. If it does fit, the next step is the written scope, what gets…

Frequently asked questions

Pricing, timelines, ownership and support — answered in plain language. Search below or browse by category.

About our process

How a project actually runs, from the first call to launch day — and what we need from you at each step.

What do you need from me before we can start?

What do you need from me before we can start?

What are the steps, from the first call to launch?

What are the steps, from the first call to launch?

How long does a project take?

How long does a project take?

How many rounds of revisions do I get, and what counts as one?

How many rounds of revisions do I get, and what counts as one?

What if I need a feature in the future?

What if I need a feature in the future?

What exactly do I receive at handoff?

What exactly do I receive at handoff?

About pricing

What a site costs, what the price does not include, and what happens when the scope grows after launch.

How much does a website cost?

How much does a website cost?

What is not included in the price?

What is not included in the price?

How and when do I pay?

How and when do I pay?

How much does maintenance cost?

How much does maintenance cost?

Which tier do I need?

Which tier do I need?

Do you offer refunds? What if I cancel?

Do you offer refunds? What if I cancel?

About the technical side

Hosting, performance, SEO, integrations and migrations — the parts that decide whether the site holds up once it is live.

How do I learn to use the admin panel? Is there training?

How do I learn to use the admin panel? Is there training?

Can you connect it to my CRM, calendar, newsletter or analytics?

Can you connect it to my CRM, calendar, newsletter or analytics?

Can the site be in two languages? Who writes the translations?

Can the site be in two languages? Who writes the translations?

Will my site be fast, and will it show up on Google?

Will my site be fast, and will it show up on Google?

How fast do you respond if something breaks?

How fast do you respond if something breaks?

What happens after the site goes live? Is there a warranty?

What happens after the site goes live? Is there a warranty?

FAQs

Any other doubt?

Feel free to reach out so we can clear any doubt you have on mind.

Frequently asked questions

Pricing, timelines, ownership and support — answered in plain language. Search below or browse by category.

About our process

How a project actually runs, from the first call to launch day — and what we need from you at each step.

What do you need from me before we can start?

What do you need from me before we can start?

What are the steps, from the first call to launch?

What are the steps, from the first call to launch?

How long does a project take?

How long does a project take?

How many rounds of revisions do I get, and what counts as one?

How many rounds of revisions do I get, and what counts as one?

What if I need a feature in the future?

What if I need a feature in the future?

What exactly do I receive at handoff?

What exactly do I receive at handoff?

About pricing

What a site costs, what the price does not include, and what happens when the scope grows after launch.

How much does a website cost?

How much does a website cost?

What is not included in the price?

What is not included in the price?

How and when do I pay?

How and when do I pay?

How much does maintenance cost?

How much does maintenance cost?

Which tier do I need?

Which tier do I need?

Do you offer refunds? What if I cancel?

Do you offer refunds? What if I cancel?

About the technical side

Hosting, performance, SEO, integrations and migrations — the parts that decide whether the site holds up once it is live.

How do I learn to use the admin panel? Is there training?