AI that earns its place.
Software that holds up.
Bx Labs is a web, mobile and AI agency, and a product studio, based in Paris. We build your website and your search visibility, your iOS and Android apps, your AI agents and your business software. One senior technical contact, from scoping through to production.
- Source code handed over
- One senior technical contact
- A reply within 24 hours
- A deliberately small number of projects
What we build
Three services, one technical foundation.
Service 01
Website & SEO
A fast site, findable in Google and in AI answer engines alike, plus business email that actually lands in the inbox.
Company site, landing page or shop: pages are rendered statically wherever the content allows it, so there is nothing left to compute when someone visits. Technical SEO, local SEO and your domain’s email are part of the work, not an option sold later. No ranking is promised — the site itself is sound and measurable.
- A fast site, statically rendered wherever the content allows it
- Technical SEO: URLs, markup, structured data, sitemap
- Local SEO and Google Business Profile
- Visibility in AI answer engines (GEO)
- Business email on your own domain, with SPF, DKIM and DMARC
Service 02
Mobile app
One codebase for iOS and Android, shipped to both stores and maintained well past launch day.
One codebase drives both iOS and Android, which cuts the work without taking anything away from what the user sees. Shipping to both stores is part of the engagement, with developer accounts opened in your company’s name. And because an app does not stop on release day, we take on what comes after: fixes, updates and OS version upgrades.
- iOS and Android from a single codebase
- Published on the App Store and Google Play
- Push notifications
- Offline mode, syncing once the network returns
- A dedicated back end and API
Service 03
AI agents & business software
Agents and business tools wired to your real data, integrated with your existing systems and supervised once in production.
An agent that answers from your own documents, an automation that absorbs a process costing hours every week, an internal tool that replaces a spreadsheet nobody can hold any more: the starting point is always a specific task, never a demo. The tool plugs into the systems you already run rather than forcing you to key everything in twice. Once in production, it stays supervised.
- Agents wired to your real data
- Automating the processes that cost hours every week
- Business applications and internal SaaS
- CRM, ERP and invoicing integrations
- Supervision in production: logs, alerts, fixes
How we work
Four stages, no six-month tunnel.
Scope
A call, your tools, what is costing you time. We name the business problem, the number that will say whether it worked, and the first piece of work to open.
Design
Flows, mock-ups, architecture and model choices. You see what it will look like and what it is built on before a single line is written.
Build
Short cycles, a demo at the end of each one, and direct access to the person writing the code. No six-month tunnel, no account manager in between.
Operate
Release, logs, fixes, scaling: the system stays watched after it goes live. And the code is handed over to you.
What we build with
Few tools, known well.
We deliberately pick few technologies, and we know them well. An exotic stack is paid for twice: once when it has to be written, and again when it has to be maintained or handed to someone else. The ones below are proven, widely documented and easy to pick up — which is what makes the code genuinely usable once the engagement ends.
Languages & core
- TypeScript
- Python
- SQL
Web
- React
- Next.js
- Node.js
Mobile
- React Native
- Expo
Data
- PostgreSQL
- Vector search
AI
- Language model APIs
- RAG
- Tool-using agents
Infrastructure
- Containers
- Continuous integration
- Managed hosting
The studio
An independent studio, run hands-on.
Bx Labs is a web, mobile and AI agency, and a product studio, both run hands-on by their senior technical founder. No account manager in between: you talk directly to the person who designs, writes the code and ships it. We deliberately cap how many engagements run in parallel — that cap is what makes the attention on each of them real.
The studio also publishes software of its own. The first is a conversational agent that answers your customers on your website, on your messaging channels and on your inbound calls; the ones after it are announced on the products page as they arrive.
- Based in
- Paris, France
- Structure
- One senior technical founder
- Services
- Web · Mobile · AI
- Languages
- Français · English
- Engagements
- A capped number in parallel
Frequently asked questions
What people ask us before we start.
Who owns the code?
You do, all of it. The source code, the repository, the domain name and the hosting accounts are created in your name or transferred to you at the end of the engagement. We keep no access you would depend on: changing supplier must never cost you your tool.
How long before a first version is in production?
A few weeks, provided the first scope is cut down to what actually solves the problem. It depends on the size of the project, on whether your data is available, and on the sign-offs you need on your side; we do not give you a date before scoping, and a date given without scoping commits nobody.
What kind of companies do you work with?
Independents, small and mid-sized companies with no in-house IT, and product teams that want senior technical reinforcement on one specific piece of work. The number of engagements running in parallel is deliberately capped: that is what keeps us reachable and keeps the cycles on time.
What does a first conversation look like?
A call to understand your business, the tools you use today and what is costing you time. You then receive a written scope — the problem as we understood it, what is feasible, what is not — followed by a proposal with a first scope and a plan. Nothing is committed until that document suits you.
What happens after go-live?
Going live is not the end of the engagement. Logs and errors are watched, fixes are applied, and scaling is dealt with as usage grows. You know who to write to, and it is the same person as during development.
How is data handled when a language model is involved?
That is an architecture decision, and it is settled during scoping: a call to a model API, execution on infrastructure you control, filtering or anonymising before anything is sent. We tell you what leaves your systems, where it goes and what is retained, according to how sensitive the data is. We sell no certification and no promise of compliance.
Contact
Tell us what you want to automate, or to build.
Book a 30-minute call with a senior technical contact: the context, the tool involved, the deadline. Pick your slot in the calendar, without leaving this page.
Book a 30-minute call
Loading the calendar…
The calendar is provided by Cal.com. It receives the technical data of your connection, sets a cookie on its own domain, and it is the one that handles the booking.
What that involves is set out in our privacy policy.
Calendar not showing? You can still book on cal.com.