04 / FAQ
The questions clients actually ask.
Who exactly works on my project?
Each project gets a lead engineer who owns it from kickoff onward. They write the code, deploy it, and answer when something breaks. The rest of the team backs them up: design, second pair of eyes on critical code, infrastructure on call. You always know whose name is on your build.
What if my lead engineer leaves Bineks?
Every project has a documented runbook in our Redmine. If a lead engineer leaves, the next engineer in the team picks it up from the runbook, not from scratch. The infrastructure stays the same, the codebase stays the same, your site stays the same.
What does engagement look like?
Three formats. One-shot teardown for $400, written analysis only. Fixed-scope build for $2k to $10k, including hosting in year one. Monthly retainer for ongoing work and hosting from $400 a month. No setup fees, no contracts longer than 12 months.
What technologies do you NOT take on?
No Wix, Squarespace, Tilda or other closed builders. No Shopify, we prefer WooCommerce for stores under 50k SKUs. No mobile apps, native or hybrid. No game dev, no blockchain, no AI agents. We focus on websites and web apps that need to last.
Can I move my site off your hosting later?
Yes. We don't lock anything in. The codebase is yours, the database is yours, the deployment scripts are yours. We hand over a tarball and a README, and your next team can run it on any provider that supports Docker.
How many projects do you run in parallel?
Six to eight active builds at any time, plus ongoing maintenance for 40+ live sites. Each lead engineer handles one or two active builds, never more. This is why we don't take every project that comes through.
Why no discovery calls?
A 30 minute call to "explore the project" is 30 minutes both sides could spend writing or reading something concrete. The teardown is faster, more useful, and you can forward it to your team. If we both want a call after that, we have one.