FAQ
Questions we get before a project starts.
Straight answers on how Bullstack works, what we build, how we scope and ship, and what you own when it is done. A Swiss full-stack software studio just outside Zürich.
Jump to
The studio
What does Bullstack do?
We build SaaS platforms, applied AI, cloud infrastructure, and websites. Usually as the outside team on a company's own product, sometimes as the engineers behind another agency, under their name.
Where are you based?
Just outside Zürich, in Spreitenbach, Aargau. We work with clients across Switzerland, Liechtenstein, the DACH region, and internationally, remote or on site.
How big is Bullstack?
Small on purpose. Big enough to build a platform end to end, small enough that your project never sits in a queue and you always know who is working on it.
Who actually builds my software?
A named core, plus people we have built with for years, picked for your project. You meet everyone on your build, you talk to them directly, and the list does not change halfway through.
Is Bullstack a freelancer network with a website?
No. A network hands you a list and takes a cut. We take responsibility for the outcome: scope it, price it, build it, and stay on it after launch. One contract, one team, one point of contact.
Why do you not show client logos or case studies?
Most of what we build runs under someone else's name or under NDA. Our clients prefer it that way. What we show instead is how we work, in the laboratory and on this site.
Do you build your own products?
Yes. We run our own software alongside client work, and what we learn building it goes back into what we build for you.
What kinds of companies do you work with?
Companies with something real to build and a reason it matters now, from funded startups to established businesses replacing systems they have outgrown. We do not list industries on the site because the work is usually confidential.
Getting started
How do I start a project with Bullstack?
Send a short written brief: what you are building, why now, what is in the way, and any timeline you are working toward. We read every project and come back within 1–3 working days.
How fast do you respond?
Within 1–3 working days, including the projects we turn down.
What should I include in the first message?
Enough to judge the shape of the work without a meeting: the problem, who it is for, what you have tried, what systems you run today, and when you need it live. Links to docs or a repo help, but a clear paragraph is enough to start.
Do you take every project?
No. We only take on work we know we can deliver well. If we are not the right team, we say so early and point you somewhere better when we can.
Can we meet in person?
Yes. We are based in Spreitenbach, between Zürich and Baden. Zürich, Baden and Aarau are half an hour away, Basel, Bern, Lucerne and Zug about an hour. We also travel to the rest of Switzerland and abroad. Call, video, a visit to your office, or email only: you choose what suits the project.
Do you work in English and German?
Yes. We work in both languages across documentation, calls, and written scope. Tell us which you prefer at the start.
Pricing, scope & timeline
What does a project cost?
It is scoped before it is quoted. After a short call you get a written estimate and timeline, before anything starts. Cost tracks scope, and we tell you the rough shape early.
Do you charge hourly or fixed price?
Mostly hourly, based on a written estimate. You see the effort as it happens in clear reporting, and we flag early if anything shifts. For clearly defined packages we also offer fixed prices.
Can you give a ballpark before a call?
Sometimes, from a short written brief. For anything non-trivial we need one conversation to fix scope before a number means anything. We will not invent a figure to win the conversation.
How long does a project take?
Most builds run four to twelve weeks from scope to launch. Smaller work is faster. The date is in the scope document, and we hold it or flag it early.
How do you structure delivery?
Two-week increments with working software at the end of each one, always on staging before production. You see progress regularly, not only at the end.
What happens after launch?
We go live, stay close through the first weeks of real use, and fix what shows up. After that we keep looking after your system: maintenance, security updates and new features. If you would rather run it in-house, we hand it over fully documented.
What do I own when the build is done?
All of it. Code, infrastructure, accounts, in your name from day one. We are glad to keep looking after it, and since nothing locks you in, you stay because it works.
Products & platforms
What product work do you take on?
Customer portals, internal tools, SaaS products, marketplaces, and the integrations between them. If the thing you need to run on does not exist yet, or the one you have no longer fits, that is the starting point.
Can you take over an existing project?
Usually. We read the codebase first and tell you straight whether it is worth continuing or worth replacing. That read is free.
What if someone drops off mid-project?
The core stays constant and holds enough of the build to keep it moving. There is a bench behind it, not a single point of failure, and you would hear it from us before it touched a deadline.
Do you build MVPs?
Yes, when the goal is a real first release in production, not a throwaway prototype. We scope to what you need to learn from real users, then build it properly enough to extend.
Can you migrate us off our current system?
Yes. We assess the old system first, map what must move, and run migration and cutover as part of the same scoped build. Replacing and extending follow the same process.
Do you build mobile apps?
We focus on web applications and APIs. For mobile we usually ship a strong web app or API your mobile team can build on, or partner where native work is the right call.
Can you integrate with our existing tools?
Yes. ERP, CRM, payment providers, identity systems, and internal APIs are normal parts of a build. We map integrations in scope so nothing is assumed.
Applied AI & automation
What applied AI work do you do?
Retrieval over your documents, structured extraction, support copilots, and agents wired into the tools you already run. We start from the process that is losing you money, not from the model catalog.
Where does applied AI actually pay off?
Repetitive document work, search across internal knowledge, triage and drafting in support, and workflows where a human still signs off. We map the current cost before we propose a pilot.
Will our data be sent to third-party AI providers?
Only where you agree in scope, with residency and retention written down. We can run models in your cloud, use Swiss or EU hosting, and keep sensitive data out of public APIs when the work requires it.
Can AI agents run actions in our systems?
Yes, with constrained tools, full action logs, and human review on anything irreversible. Agents are scoped like any other integration, not given open access by default.
How do you measure whether an AI pilot works?
We define success metrics before build: time saved, error rate, coverage, or cost per task. You get an evaluation harness so quality is tracked after launch, not guessed from demos.
Infrastructure & cloud
What infrastructure work do you take on?
Kubernetes, CI/CD, observability, Linux hardening, and the automation around releases. We set it up so updates become routine. We can run it for you, or set everything up so your team can.
Can you audit and reduce our cloud spend?
Yes. We review what you run, find spend that is not earning, and fix or remove it. Savings are part of scope when that is the goal, not a side promise.
Do you host in Switzerland?
We can. Hosting runs in Switzerland, the EU, or your own cloud depending on residency, latency, and what you already pay for. Accounts stay in your name.
Do you work with Kubernetes?
Yes, including cluster setup, deployments, secrets, and the observability stack around them. We also work on simpler setups when Kubernetes is not the right answer.
Will we depend on you?
No. Everything sits in your accounts, with documentation and step-by-step runbooks. We are glad to keep running it, but you never have to rely on us.
Websites, SEO & performance
What makes a website that converts?
Fast load, clear message, structure that matches how people search, and copy that reads like your best salesperson. We build marketing sites in Next.js with real performance budgets, not template stacks.
Do you handle SEO and structured data?
Yes. Canonical URLs, metadata per page, sitemaps, robots rules, and JSON-LD where it helps search and answer engines quote you correctly. Technical SEO is part of the build, not an add-on.
How fast should a marketing site load?
Under a second on a good connection is the target. We self-host fonts, avoid render-blocking third parties, and treat largest contentful paint as a hard budget.
Can you rebuild our site without losing rankings?
Yes, with a migration plan: URL mapping, redirects, preserved content signals, and staged cutover. We treat search traffic as production traffic.
Technology & stack
What technologies do you use?
Next.js, React and TypeScript on the front end, Node.js and Postgres behind it, Python where the work is data or ML. Kubernetes, Terraform, Docker and CI/CD for infrastructure, observability wired in from the first deploy. Hosting in Switzerland, the EU, or your own cloud.
Why Next.js and React?
They are fast to ship in, strong for SEO and performance, and easy for your team to hire for later. We pick the stack for maintainability and speed to production, not trend.
Do you work with PHP, Laravel, .NET, or Java?
Yes. We maintain and extend systems in Laravel, Symfony, Spring Boot, and .NET as well as greenfield TypeScript. The stack page lists what we build with regularly.
Can you work with our existing stack?
Usually. We match your conventions where they are sound, and say clearly when we would recommend a change. The first read of your repo is part of how we decide fit.
Security, data & compliance
What about our data?
Everything runs in your accounts, under your control. We work to the Swiss nDSG and the GDPR, and can keep data in Switzerland or the EU.
Are you GDPR and Swiss nDSG compliant?
We process personal data accordingly in our own operations and build client systems to respect both frameworks. Data processing agreements are part of engagement when you need them.
Where is code stored?
In repositories you own from day one, typically on GitHub or GitLab in your organisation. We do not keep a private fork as leverage.
Do you sign NDAs?
Yes. Confidentiality is normal for the work we do, especially under agency and enterprise engagements.
Agencies & white-label
Do you work under our agency's name?
Yes. You keep the client, the relationship, and the invoice. We build under your name and stay out of the way.
Can you white-label engineering for our clients?
Yes. We join your calls when you want us there, stay off them when you do not, and never contact your client unless you ask us to.
How do you communicate with agency partners?
You choose the channel and cadence. We align on scope, staging access, and who speaks to the end client before build starts so nothing surprises anyone at launch.
Switzerland & regions
Do you work with companies outside Switzerland?
Yes. We work remotely across Europe and beyond. Time zone overlap with Central Europe is straightforward for most engagements.
Do you serve Zürich, Zug, Basel, and Bern on site?
Yes. From Spreitenbach we reach Zürich in half an hour and Zug, Basel and Bern in about an hour. We visit clients across Switzerland and abroad whenever the project benefits from it.
Why a studio just outside Zürich?
Close to the market without Zürich office overhead. You get senior engineers and short paths to the people who plan and build your project, with Swiss residency and data options when you need them.
Did not find your question?
Tell us what you are building and what is in the way. We reply within 1–3 working days with an honest read.
Tell us what you're building