→ man faq --cat=all
money, scope_and_timeline, who_does_the_work,
ownership_and_contract, after_launch, what_we_do_not_do
✓ includes the questions most studios skip
// faq
Thirty answers, including the uncomfortable ones.
If a question only has a good answer when we are talking to you, it belongs on this page. Where the answer is "no", it says no.
Pricing and money
The questions about cost that people find hardest to ask directly.
How much will my project cost?
There is a range on our pricing page and a number in your proposal, and they are different things. The range tells you whether we are in your budget at all. The number comes from a written scope. We do not send a figure before we understand the work, because a number produced without understanding is a guess with a logo on it.
Do you work hourly?
No. Hourly billing punishes efficiency: the faster we get, the less we earn, and the more expensive it is for you to find a shortcut. A fixed price keeps speed as our problem and budget control as yours. Where work is genuinely undefined, we would rather use a sprint or a retainer than sell you a fixed price we cannot stand behind.
Do you charge for discovery and scoping?
Yes, as its own fixed-fee phase. Folding it into the build price would hide the cost of learning what you actually need, from both of us. The discovery fee is credited in full to the build invoice, and you keep the scope, the assessment and the plan whether or not we go on to build.
What are your payment terms?
Milestones defined in the contract, invoiced against what has shipped, with a deposit at signature. We do not publish one universal schedule because a four-week design system and a six-month platform build do not share a sensible one. Ask for the schedule with your proposal and it is written down.
My budget is below your published range. Is there any point talking?
Yes. The range describes a category, not your project. Usually the answer is to cut scope - fewer screens, a simpler integration, a later phase - rather than to hope. An honest smaller fixed price beats a larger one that slips.
Will you work for equity instead of fees?
Not as a default, and we would push back if it were the whole arrangement. Equity-only leaves a studio unable to cover its own costs, and that failure lands on you at the worst possible moment. For genuinely early-stage work it can be part of a larger conversation. Ask us directly and we will give you a straight answer for your situation.
Scope, timeline and process
Dates, deadlines, and what happens when reality disagrees with the plan.
How long will it take?
Ranges by category: discovery is one to three weeks, a focused design system four to eight weeks, a substantial platform build several months. Those are bands, not a promise. A date that means anything only comes with a scope, because a date without one is just a guess with a calendar attached.
Can you do it faster?
Sometimes, and it costs. Parallelising work, adding people, and accepting a less resolved design all buy time. We will tell you what each option costs in money and in quality before you choose, rather than quietly absorbing it and missing a date.
What happens if you run late?
That is our failure and it is handled as one. If we are late, we say so early rather than at the deadline, we tell you the new date and why, and the contract sets out what that costs you. If it was a change request you approved, the date moved with the scope rather than despite it.
What happens if the scope changes mid-project?
You get a written change request with a description, an effort estimate, a price and a schedule effect, and nothing is built until it is approved. If we misunderstood the scope, that is not a change request - it is our problem and we fix it at our cost.
How many revisions are included?
Revising the work until it is right is part of delivering it, so we do not sell you a revision count. What is limited, and priced, is scope change - a feature you did not originally specify is not a revision. The distinction is between making something good and adding something new.
How do we actually start?
You send a brief. We reply with questions inside a day. A scoping conversation follows, then a fixed-fee scoping phase, then a written scope and a fixed price. Four steps, and you can stop after any of them. There is no sales sequence after the proposal.
Who does the work, and AI
The questions about the humans and the tools behind the output.
Who will actually build my project?
A pod: a tech lead who owns architecture and delivery, engineers, a designer, and QA, with growth capacity where the engagement needs it. Ask who will be on your project and at what seniority before you sign, and you will get a written answer. We do not publish individual names or bios, by policy.
Will I get the people you pitched?
Yes. This is a small studio, which means the people who present the work are close enough to the delivery that pretending otherwise would collapse within a fortnight. If capacity is genuinely committed elsewhere, we tell you before we accept.
Do you subcontract the work out?
Your project is delivered by the studio pod, working inside your accounts and your repository. Where a task genuinely needs a specialist the studio does not hold in-house, we bring someone in and tell you that they are involved. We do not pass your work to an agency you never see and invoice you a margin on it.
Do you use AI to write my code?
Yes, and we would rather be precise about it than vague. It is used for boilerplate, scaffolding, documentation drafts, test scaffolding and research. It is not used for architecture decisions or for security-sensitive code that has not been reviewed. Every line ships with a human review, and the reviewer is accountable for it.
Does AI tooling make my project cheaper?
Not visibly. It makes us faster, and a fixed fee means the speed is ours to keep rather than yours to pay for. You are not billed less because we got quicker at something. That is the entire argument for this pricing model, so pretending otherwise would undermine it.
What if I need someone to sign off on security?
Then you need an independent firm, not us. We do not perform penetration testing, SOC 2 audits, ISO certification or compliance attestation, and we hold no security certification. We can scope the engagement, provide documentation, implement controls and fix findings - but the report has to come from someone independent.
Ownership, confidentiality and contract
Who ends up owning what, and what we sign.
Who owns the code and the design?
You do, on payment. Source files, design files and repository access are yours, and IP assignment is in the contract rather than left to custom law in your jurisdiction. We list any third-party or licensed components we relied on, because those have their own terms that stay with you.
Will you sign an NDA before we even talk?
Yes, and we would rather sign yours than impose ours. Ask and we will get it turned around before any substantive conversation about your product or your data.
Do you reuse my work in other projects?
No. Generic engineering patterns and internal tooling are ours and we reuse those freely. Your product, your brand, your data and your code are not reused anywhere, and we do not publish client work without permission.
What kind of contract do you use?
A written statement of work: scope, acceptance criteria, price, milestones, change process, IP assignment, confidentiality and what happens on both sides if it ends early. A generic master services agreement with the substance left for later is not a contract, and we are happy to be challenged on that.
Can you sign our procurement paperwork?
Usually, yes, with a legal review on our side first. Send it early rather than at signature - procurement documents that arrive in the final week are how projects lose three weeks.
After launch, support and maintenance
What happens once the project is over.
What happens after launch?
Handover: repository access, a setup guide, a deployment runbook, a credential and third-party inventory, and a live walkthrough with the engineers who built it. Then you choose: a maintenance retainer, a growth retainer, sprints, or nothing at all. All four are legitimate and none is a requirement.
Do you offer support after launch?
Yes, as a recurring retainer or as a block of support time bought up front. What we do not offer is an unlimited hotline with no boundary, because a promise of unlimited help from a small studio is a promise that has to be broken quietly later.
Will you fix bugs after handover?
Defects against the acceptance criteria at handover are ours, and we fix them. Once a new request or a new requirement arrives, it is a change request like any other. The line is drawn at the scope, not at our mood.
Can you maintain something you did not build?
Yes, as a new engagement, and we will start with a short review of what exists rather than pretending to know it on sight. We will also tell you if the honest answer is that it needs rebuilding instead of maintaining.
What we do not do
The section most agencies leave out. Read this one before you commit.
Do you guarantee rankings, traffic or revenue?
No, and anyone who does is not being straight with you. Rankings depend on competitors, algorithms and factors no agency controls. What we commit to is method, measurement and an honest monthly read on what moved and why.
Do you certify us as compliant or secure?
No. WebNuvexa holds no SOC 2, ISO or GDPR certification, and certification is not something a studio can hand an organisation anyway. Data protection is an obligation you discharge through controls and records, not a badge. We do readiness work and we refer the certification itself to independent bodies.
Do you perform audits?
Not independent ones. We review our own work and each other's code constantly, and that is engineering practice rather than an assurance product. A real audit, penetration test or compliance attestation has to come from a qualified third party, because an audit by the people being audited is worth nothing.
What will you tell me before I sign that is unflattering?
That the project may be the wrong one at the wrong time, that a cheaper scope would serve you better, that our pod is not the right shape, or that you should hire someone cheaper. It happens rarely and it costs us work. It is also the only reason the word fixed price means anything on this site.
If it is not here, ask
This page covers thirty questions. There are certainly others, and the ones we cannot answer pre-project are usually the ones worth asking first.
Ask before you brief us
If you are unsure whether a project is worth doing, whether the timeline is realistic, or whether your budget supports the outcome - ask before you write a brief. Those questions are free and the answers are more useful at that stage.
You will get a real person
A senior engineer reads every enquiry and replies within 24 hours. If your question is not something we can help with, we will say so and point you somewhere that can.
Uncomfortable questions welcome
Ask about our pricing, our pod composition, our failures, or whether you should hire someone else. Those are the questions this page exists to pre-answer, and there is no wrong time to ask them.
Straight answers or no deal
If the honest answer is that we are not the right studio for the work, that is what you will hear. It costs us engagements occasionally and it is the only reason a fixed price is worth reading.
Ask us the awkward question
Tell us what you actually want to know. If we cannot answer it, we will say so rather than fill the space.