Skip to content
bsantostecnologia
Get in touch

Software engineering studio

We build the software your operation runs on and ship it.

iOS and Android apps, web apps, AI automation and the integrations that tie it all together. From first sketch to production — with the code and the infrastructure in your name.

Tell us about your projectSee how we work
studio.tsTypeScript
// what we do, written the way we write itexport const studio = {  name: 'bsantos tecnologia',  email: 'bugsantos@proton.me',   builds: [    'Mobile apps',    'Web apps and sites',    'AI automation',    'Integrations, APIs and data',  ],   handover: 'repo and accounts in your name',} satisfies Studio;

It is the summary this page spells out below — and the address your project goes to.

01 — What we build

Four practices that overlap

Every project starts in one of them and almost always needs another. That is why the app and the API it talks to come from the same place.

  • Mobile apps

    iOS and Android from a single codebase, from design through to store release.

    • Flutter for both platforms; native when the case calls for it
    • App Store and Google Play submission, review process included
    • Push notifications, offline mode, camera, maps and payments

  • Web apps and sites

    From a marketing site that loads fast to the internal dashboard your team lives in all day.

    • Next.js and React with TypeScript end to end
    • Authenticated areas, admin dashboards and signup flows
    • Performance, technical SEO and accessibility from the first commit

  • AI automation

    Work that eats people-hours today turned into an automated flow — using AI where it actually helps, and leaving it out where it does not.

    • Agents that read, classify and reply with your business context
    • Data extraction from documents, email and spreadsheets
    • Anthropic and OpenAI models wired in, with cost measured per run

  • Integrations, APIs and data

    The systems you already run, talking to each other, with data you can trust.

    • REST APIs and webhooks, with authentication and versioning
    • ERP, CRM, payment gateway and legacy system integration
    • Data pipelines, databases and infrastructure

02 — How we work

No black box at any stage

You watch the thing being built while it is being built. We do not disappear for a month and come back with a surprise.

  1. Conversation

    You write what you need. We come back with questions — the ones that change scope, not the ones from an intake form.

  2. Scope and proposal

    A document with what is in, what is out, how it is split, what it costs and how long it takes. Before a single line of code.

  3. Delivery in cycles

    Short cycles, each ending in an environment you can open and click through. You use what is ready while the rest is being built.

  4. Going live

    Deploy, store release, domain and monitoring. Delivery ends in production and working, not in a zip file.

  5. After launch

    Maintenance and further work under a separate agreement. If you would rather continue with another team, the documentation exists for exactly that.

03 — Stack

The tools we actually use

Not an encyclopedia: this is the set we build with, and what you will find in the repository once it is yours.

Mobile

  • Flutter
  • Dart
  • Swift
  • Kotlin

Web

  • Next.js
  • React
  • TypeScript
  • Vite

Backend and data

  • Node.js
  • Deno
  • PostgreSQL
  • Supabase

AI

  • Claude / Anthropic API
  • OpenAI API
  • MCP
  • Embeddings and RAG

Infrastructure

  • Vercel
  • Fly.io
  • Cloudflare
  • GitHub Actions

04 — Questions

The ones that always come up

Answered here so they do not have to cost you an email.

How long does it take?

It depends on scope, and the honest answer only exists after the first conversation. A lean first version usually lands in weeks; a full product, in months. The timeline goes in the proposal, in writing, before we start.

How does billing work?

Fixed scope or per work cycle, agreed in the proposal. Nothing starts before you know exactly what it costs and what is included.

Do I own the code?

You do. Repository, infrastructure and service accounts are in your name from day one. You never depend on us to keep the project moving.

Do you maintain it afterwards?

We do, under an agreement separate from the build. And we hand it over documented well enough for another team to take over, if that is your path.

I have a half-finished system. Can you pick it up?

Yes. The first step becomes a read of what exists, with an assessment of what is worth keeping and what costs more to maintain than to rebuild. You get that assessment even if you decide not to continue with us.

Do you work with companies outside Brazil?

Yes. Remote work, in English or Portuguese, with contract and invoicing arranged case by case.

05 — Contact

Tell us what you want to build

One paragraph is enough for us to come back with useful questions. If you already have a deadline, a budget or a running system, mention it — it shortens the path.

bugsantos@proton.me
Write us an email

Opens your mail client with an outline ready. No form, no signup.