FAQ
Questions before a brief.
Direct answers. If yours is not here, send it with the project note on the contact form.
What does Codeberry actually build?
- Mobile apps, websites, online stores, AI and workflow automation, and ongoing maintenance after launch. We take work from a written brief to a running product, then stay available if you want a retainer.
Do you only work with startups?
- No. Founders, operators inside existing companies, and brands that already sell online all show up. The common thread is that you want a small team that will own the outcome, not a bench of unused roles.
How long until we see something working?
- Most first versions are scoped to land in two to four weeks after kick-off, if the brief is clear and you can answer questions quickly. Larger products are sliced so you still see a usable piece on that rhythm instead of a six-month silence.
How do you price the work?
- We price from a written scope, usually a fixed fee for a defined first version, then a retainer if you want us to stay. We do not publish a rate card here because the mix of app, shop, and automation changes the cost. Send a brief and we will say whether we are a fit and what we would charge.
Who owns the code and accounts?
- You do. Repos, stores, cloud accounts, and domain DNS should sit in your organisation. We work inside them. A project should not leave you renting your own product from us.
Will you train or fine-tune a private model for us?
- Only if the job requires it and the data is actually yours to use. Most useful automation is retrieval, tooling, and workflow around a hosted model, with a person still reviewing exceptions. We will say no to a fine-tune that is theatre.
Can you take over a product someone else built?
- Often, yes, after a paid discovery pass: we read the repo, hosting, and risks, then we tell you what we would keep, rewrite, or refuse. We will not pretend a rescue is a two-day patch if the foundations are unsafe.
Do you work remotely?
- Yes. Kick-off and reviews are written and on calls. If a workshop in person would help, we can discuss it; it is not required to start.
What do you need from us to start?
- A short description of the problem, who it is for, and any systems you already use. Brand files, access, and examples of the current process come next. You do not need a specification document before the first conversation.
Where do I review a staging site or a TestFlight?
- In the client portal, on the Delivery tab for that project, once we have issued a preview. Until then the URL lives in the thread. Staging hosts should not be indexed. Device builds are invites, not public pages.
How do we pay?
- When Stripe is connected, invoices and checkout live in the client portal Billing tab. We do not collect card numbers on this marketing site. Demo amounts in the portal are labelled quotes, not live charges.
How do you handle privacy on this website?
- The enquiry form collects name, email, and your note so we can reply. We do not sell that list. Details are on the Privacy Policy page. Product work for a client uses the contract for that project.
Still deciding?
Write the messy version. We would rather see that than a polished deck.
Start a project