Straight answers, no rate cards

Every quote is scoped after a 20-minute call. We don't publish a rate card because "restaurant website" and "storefront with inventory sync" both get called "website," and generic pricing tricks people into paying for the wrong thing. On the call we look at what you actually need, what you already have, and what the honest scope is — you get a real number the same day. If we can't help within your budget, we'll tell you and point you somewhere that can.

Yes — 100%, including the code, the domain, the hosting account, the design files, and any AI agents we build for you. Everything ships to your GitHub, your Vercel or Hostinger, your Google Workspace. There is no BEIRUX CMS, no proprietary builder, no vendor login you have to keep paying us for. If you fire us tomorrow, another developer can pick up the repo and keep going.

Use them if your business is a template and you're fine renting your storefront from a platform that can change pricing, features, or terms on you at any time. We build for the case where you've outgrown that — custom design, real performance, Stripe integrated at the code level, and a stack you own outright. A BEIRUX site typically loads fast, ranks better because it's built for how Google actually crawls in 2026, and doesn't charge you 2% of every transaction. If a template genuinely fits your needs, we'll tell you that on the call.

Samih is the principal on every project and makes every judgment call — design, copy, architecture, what ships. Production labor (component scaffolding, image generation, first-pass copy, code review) runs through AI systems Samih directs. There are no anonymous overseas contractors, no white-labeled agencies behind the curtain, no junior handoff after the sales call. You talk to Samih, Samih owns the outcome.

It means we build and run the AI automations that would otherwise eat your evenings — lead qualification, appointment reminders, first-response to customer emails, review requests, order-status DMs — on your accounts, monitored and maintained by us. Not a chatbot widget bolted onto your site. Real workflows: an agent that watches your inbox, drafts replies in your voice, and hands off to you when it's not sure. Setup is a one-time build; then a monthly retainer keeps it running with fallbacks and observability so it doesn't quietly break — scoped to which channels and how much traffic you actually get.

Most marketing sites ship in 2 to 4 weeks from deposit. A one-page site can be live in a week; a storefront with Stripe, inventory, and email flows is closer to 4 to 6 weeks. Agent builds run 1 to 3 weeks depending on how many tools they need to talk to. The pace-limiting factor is almost always content and approvals from your side, not build time — we'll tell you upfront what we need from you and when.

You lose nothing. The site stays live on your hosting, the domain stays on your registrar, the agents keep running on your accounts. We hand off documentation and admin access on day one, not as a departure ritual. If you want to hire another developer, the codebase is standard Next.js and Postgres — any competent shop can take it over. The only thing that stops is our retainer work (maintenance, new features, agent tuning).

Yes, based in the NJ/NYC metro area — most local clients get an in-person kickoff and then work happens over email, text, and short video calls. Remote clients across the US work the same way minus the coffee. In-person isn't a requirement; a lot of our best projects have shipped without meeting face-to-face.

Head to /contact and send a short note about what you're building. Samih replies, and if it looks like a fit you'll get on a discovery call — typically 20 to 25 minutes. The call is the intake; there's no separate questionnaire to fill out first. If we're a fit, we draft a Master Services Agreement (MSA) and a Statement of Work (SOW) scoped to your project. The MSA is reused across clients; the SOW is written fresh for you.

We talk through what you actually need — not what "website" or "AI agent" gets marketed as, but the honest scope of your business, what you already have, and what would move the needle. You walk out with a real number and a straight answer on whether we're the right shop. If we're not, we'll say so and point you somewhere that fits better.

Two patterns don't work. First, price-shopping for a template site — if the goal is the cheapest thing that resembles a website, a Squarespace or Wix template will serve you better and we'll tell you that. Second, projects that need to touch protected health information (HIPAA) or ship to EU data subjects under GDPR — those need infrastructure and legal posture we don't run. We'd rather turn down the project than pretend we can do it well.

No. Most clients arrive with a vague sense ("I need a better site," "I want to automate this") and the call is where it gets sharp. Bring what you have — current site, existing tools, the problem you're trying to solve — and we'll do the scoping together.

Most sites are Next.js (React, Tailwind, Framer Motion) deployed on Vercel with a Postgres database (Neon) when they need data. Some clients — especially storefronts with legacy PHP infrastructure — get a Vite static build with PHP endpoints on Hostinger. We match the stack to the project, not the other way around.

Primary is Vercel — the site auto-deploys from GitHub every time we merge to main, so shipping is fast and rollback is one click. For clients with existing Hostinger accounts or PHP requirements, we host there. Either way, the account is yours, in your name.

None by default — content lives in code and ships with the site, which keeps performance high and the surface area small. When a client needs to self-edit, we build a custom admin panel scoped to the fields that actually change (menu items, product prices, blog posts) rather than dropping in a generic CMS.

Latest two versions of Chrome, Safari, Firefox, and Edge. Older browsers may work but aren't a target. If your audience skews toward legacy browsers, tell us on the discovery call and we'll factor it in.

WCAG 2.0 AA is our target — semantic HTML, keyboard navigation, visible focus states, contrast baselines. A formal WCAG audit is only run if you request and scope one, but the target is baked into how we build.

WebP with responsive sizing so mobile visitors don't download desktop-sized files. Alt text on all content images. Full-resolution masters are delivered to you so you always have the originals — we don't lock your images behind our tooling.

Sitemap, robots.txt, canonical tags, JSON-LD structured data, and an llms.txt file for AI crawlers (ChatGPT, Claude, Perplexity). On-page SEO — titles, descriptions, headings — is reviewed page by page. What we don't do: promise you a ranking, because nobody credible can.

Two rounds per deliverable by default — the MSA sets this and each SOW can override it up or down. Additional rounds are billed at our standard rate. Most projects don't hit the ceiling; the two rounds exist as a stop against endless nudging on colors nobody remembered mattered.

In our experience, almost always client-side content and approvals — copy that takes weeks to sign off, logos that never arrive, decisions that need a partner who's on vacation. Build time is predictable; content velocity is not. We'll tell you upfront exactly what we need from you and when, so the ball doesn't sit in a court nobody's watching.

You do — 100%. On full payment of an SOW or milestone, all rights in the work assign to you: code, design, copy, structured data. Until payment, the work-in-progress belongs to us, which is how we protect against a project that ships and never pays. Once you're paid up, it's yours to modify, extend, or hand to another shop.

You do, at all times. Even when we buy or register the domain on your behalf during setup, you're the beneficial owner from day one. On request or at termination — with invoices paid — we transfer registrar access to you. There's no scenario where BEIRUX holds a domain hostage.

Internal frameworks, reusable code, templates, and proprietary tools we bring into the project stay ours — but you get a license to use them as embedded in your deliverables. Third-party licenses (Canva assets, fonts, POS integrations) stay subject to their own terms, which we'll flag if any of them matter to your build.

You keep the site, the domain, the hosting account, and any agents we built (the agent code is yours to redeploy to your own Cloud Run project or equivalent runtime). Termination is month-to-month with 14 days' written notice before the next renewal date — no long contracts, no exit fees. Undisputed completed deliverables are released regardless of any payment dispute over other items. Domains, emails, and other assets get handed over on request once you're paid up.

90 days after termination, then hard-deleted, unless you request earlier deletion. This gives us a buffer for a final export or a "we forgot one thing" request, without leaving your data sitting around indefinitely.

Three years for general confidential information; indefinite for trade secrets. That's mutual — the confidentiality obligations bind both sides. Non-solicitation runs 12 months post-termination.

Yes, and this is deliberate. The stack (Next.js, React, Postgres, standard Tailwind) is common enough that any competent shop can take over. Code lives in your GitHub, deployment lives in your Vercel or Hostinger, database lives in your Neon account. There's no BEIRUX runtime you'd be cut off from.

Databases on Neon Postgres carry 6-hour point-in-time recovery — we can rewind to any point in the last 6 hours. Firebase Storage carries object versioning for uploaded files. Hosting-provider SLAs (Vercel, Hostinger) apply to the hosting layer itself. Anything beyond that (nightly exports to a separate cloud, cross-region replication) is a scoping conversation.

Yes. Most clients continue on a maintenance-and-hosting retainer after launch — this covers the hosting bill, keeps dependencies and security patches current, and gives you a channel to send small updates without a new SOW every time. The specific inclusions are scoped per client based on what your site actually needs.

Yes, on inherited sites where the stack is one we support (Next.js, Vite/PHP on Hostinger, WordPress in some cases). We'll do a short audit first to make sure the codebase is in a state we can responsibly take over — we'd rather turn it down than pick up a mess we can't stand behind.

If it's an error in something we built and shipped, we fix it — that's the standard-of-work clause. Time to fix depends on severity and whether you're on a retainer; retainer clients get priority. If a break traces to a change on your side or a third-party service (Stripe, your email provider), we'll diagnose it and give you options.

New Jersey. Venue for any dispute is Middlesex County — state or federal court there.

Our MSA sets a 3-step dispute process. First, good-faith negotiation between the two of us. Second, if that doesn't resolve it, mandatory mediation in Middlesex County, NJ. Litigation is only available after mediation has been attempted. Prevailing party recovers reasonable attorney's fees. In practice, we've never come close to step two — the change-order and payment terms are designed to prevent the ambiguity that leads there.

Month-to-month, auto-renewing. Either side can terminate for convenience with 14 days' written notice before the next renewal date. No annual lock-in.

Our limitation of liability caps our exposure at the amount you paid us for the services giving rise to the claim, and excludes indirect/consequential losses (lost profits, downstream damages). This is standard for professional services at our scale and reflects the fact that we don't currently carry professional liability (E&O) insurance — which is disclosed in the MSA, not buried.

No — nobody credible does. We don't promise sales figures, follower counts, search rankings, or revenue. What we do promise is professional effort against a clearly scoped SOW, human-reviewed output, and correction of our own errors at no charge. If someone else is promising you a #1 Google ranking, that's a signal to be careful with them, not a benchmark we're falling short of.

Not currently. This is disclosed in MSA §18, and our limitation of liability reflects it. It's a real thing to know before you sign; we'd rather tell you than have it be a surprise later.

We can review a client-supplied MSA, but our default is our own — it's been through counsel, it fits how we actually work, and it saves both sides the redline round. If your legal team has hard requirements, bring them up on the discovery call so we can figure out fit before we're deep into scoping.