Straight answers.
Including the awkward ones.
What things cost, how long they take, and what nobody in this industry can promise you. If an answer here is uncomfortable, it is still the true one.
Ask something else ↗Twelve questions, answered plainly.
Grouped by what they are about. Open one and the rest collapse, because twelve open answers is a wall rather than a page.
Working together
You work directly with the person doing the work. BZ Development is a small studio, not an agency with account managers relaying messages between you and an unnamed delivery team.
Every engagement starts with measurement, not a proposal. We audit the current state, rank the findings by what they cost you, and only then scope the work. You approve that scope before anything is built.
Yes. The work is remote and the deliverables are code and reports, so location rarely matters. Timezone overlap for calls is worth checking before we start.
We say so, before you commit money to it. Talking a client out of work that will not pay off costs one project and keeps a reputation, which is the better trade.
Pricing and terms
Pricing depends on scope, which is why it follows the audit rather than preceding it. Send the site URL and what you are trying to fix, and you will get a scoped estimate rather than a number pulled from a rate card.
Both. Technical fixes and builds usually work as fixed-scope projects. Content systems and ongoing SEO work better as a retainer, because the value compounds over months rather than arriving at handover.
You do. That includes the repository, the deployment configuration and the documentation. There is no proprietary layer that would require us to stay involved.
Technical
No, and treat anyone who does with suspicion. Rankings depend on competition and on Google's algorithm, neither of which any agency controls. What can be guaranteed is that the technical barriers to ranking get removed and that progress is measured honestly.
Technical fixes to indexation often show within days. Ranking movement typically takes weeks to months, and content-driven growth compounds over two to three quarters. Any firmer number than that is a guess presented as a promise.
Yes for audits, performance work and technical SEO. Those depend on what the crawler and the browser receive, which is platform-independent. New builds are usually Next.js, because it gives the most control over speed and rendering.
As a drafting tool, behind quality gates. Drafts are checked against voice rules and a factual-sourcing requirement: any draft citing a number without a verifiable source does not ship. The gates matter more than the drafting method.
Builds target WCAG 2.2 AA: keyboard navigation, sufficient contrast, correct semantics and screen-reader support. Accessibility overlaps heavily with SEO, since both depend on well-structured, machine-readable markup.