Frequently Asked Questions
Everything you need to know about BuildPreview.
How does a BuildPreview engagement work?
Send a short note through the contact form about your build, deadline, and stack. You get a focused reply with a scoped plan and the next best step — build path, timeline, and whether a codebase from our library shortens it — before any work begins.
What does a website or business system cost?
A focused website package starts from KES 45,000. Ecommerce, portals, and custom systems are scoped around the actual workflow, integrations, and launch needs. Before work begins, you receive a written proposal that makes the deliverables and any third-party costs clear.
How long does a project take?
Timing depends on the scope, content readiness, decision speed, and integrations required. A focused website can move quickly; ecommerce, portals, and custom workflows need more planning and testing. We agree on a realistic delivery plan before the build starts.
What is included in a website package?
Every website package includes responsive implementation, clear enquiry or conversion paths, basic on-page SEO foundations, testing before launch, and a practical handover. Higher-scope work adds pages, integrations, custom workflows, or ecommerce features where agreed.
Who owns the website, code, and accounts after launch?
You retain ownership of the work and the accounts created for your project. Credentials, third-party services, ongoing costs, and handover items are made clear as part of the agreed scope.
Can I still buy a codebase standalone, without a service?
Yes. The codebase library is permanently available as a self-serve tier. Each product runs on its own checkout flow with instant delivery, documentation, and demo links. Engaging BuildPreview for customization or deployment is optional.
What does a retainer include?
A retainer reserves an ongoing window of engineering hours you control — priority fixes, feature tweaks, dependency upgrades, and integrations — with a short monthly summary of what shipped and what is queued.
Do you handle deployment and hosting?
Yes. Deployment support covers hosting setup, SSL, environment configuration, email, payment integration, production build fixes, and go-live checks against a verified build.
What technologies does BuildPreview work with?
Modern stacks such as React, TypeScript, Node.js, PHP/CodeIgniter, Supabase, PostgreSQL, MySQL, and common hosting platforms — both inside existing codebases and from greenfield builds.
How do I get started with a custom project?
Use the contact form, include the product, feature, or business workflow you want to build, and you’ll get a practical reply instead of a slow sales cycle.
Do you offer refunds on codebases?
Because digital products download immediately, refund requests are reviewed case-by-case. Engaging BuildPreview before purchase lets us confirm fit and scope first, reducing the need for refunds.
Where can I see demos of the codebase library?
Live demos are available from each product detail page when a demo is provided for that codebase; the library home also lists example categories.
Can BuildPreview rescue a project built elsewhere or by another team?
Yes. The rescue pillar reproduces the failure, fixes the root cause, stabilizes the build, and documents the path forward — scoped and time-boxed.
How long does support last after a build?
Support duration depends on the engagement: one-off builds include an agreed post-ship window; retainers cover ongoing support for as long as you keep the window active.
Can BuildPreview work with businesses outside Nairobi?
Yes. Discovery, design review, implementation, and handover can be run remotely with shared previews and clear communication. The right delivery rhythm is agreed during scoping.