Custom projects
We build the site, store or application you need
Websites, WooCommerce stores, web applications, mobile apps and integrations — built by the same team behind the Infixs plugins, with the same stack we use in our own products. Tell us what the software has to do and we will come back with questions or a written scope, not an automated reply.
Public numbers, verifiable on WordPress.org — we don’t publish figures you can’t check.
What we build
Software that has to run in production and keep working — the same standard we hold our own products to.
Websites
Institutional sites, landing pages and content sites — fast, indexable and easy for your team to edit.
- Built on WordPress or Nuxt, depending on who maintains it after launch
- Multilingual when you need it — this site runs PT-BR and EN
- Forms, analytics and tracking wired up before launch
Online stores
WooCommerce stores: new builds, replatforming, and rebuilds of stores that outgrew their theme.
- Checkout, shipping and payment configured for how your business actually sells
- Product and customer data migrated and tested before launch day
- Custom plugins when no decent plugin exists for the requirement
Web applications
Internal tools, dashboards, customer portals, admin panels — the work being done in spreadsheets today.
- User accounts, roles and permissions modelled properly
- Reports and exports your team can run without a developer
- Deployed and updated continuously, not delivered once as a zip
Mobile apps
Scoped case by case, starting from which kind you actually need — for a lot of business software, an installable web app is faster and cheaper than a native build.
- We recommend the approach in the first conversation, with reasons
- Web-first where it fits; native evaluated against the real requirement
Integrations & automation
Connecting systems that were never designed to talk: ERP to store, store to marketplace, form to CRM.
- API integrations, webhooks, scheduled jobs and data syncs
- Retries, logging and failure alerts — an integration that fails silently is worse than none
- Repetitive manual tasks turned into supervised automation
Store rescues
Slow store, heavy queries, checkout that fails under load: measured first, then fixed.
- Diagnosis based on measurements, not guesses
- If a plugin we already sell solves it, we will say so and send you there instead
The stack we actually use
We don’t pick a new framework per project. We build on the tools we use in our own products — which is why we can maintain what we ship.
If your project lives in a different stack, say so early — sometimes the right answer is working inside what you already have, and sometimes it’s us telling you we’re not the right team for it.
How a project runs
The same sequence every time. No stage starts before the previous one is written down.
What you receive
A project is finished when someone other than us can run it, change it and deploy it.
The source code
Delivered in a Git repository with full history. Ownership terms are stated in the proposal — our default is that code written for your project is yours.
Accounts in your name
Hosting, domain, DNS, cloud project, API keys — registered to you. We hold access while we work, and you can revoke it.
Documentation
How to run it locally, deploy it, and where everything lives — written for the developer who inherits it.
A handover session
A walkthrough with whoever will operate the system: the admin, the moving parts, and what to check when something looks wrong.
How pricing works
Two models, chosen by how well the requirements can be written down — not by which is more profitable for us.
Fixed scope, fixed price
When the requirements can be described precisely, we write them down and price them.
- You know the total and the delivery terms before signing
- The scope document says what’s excluded as explicitly as what’s included
- Anything outside the scope is quoted as a change before it’s built
Hourly or monthly
When the requirements will move: product discovery, continuous development, maintenance.
- The honest model when priorities genuinely change month to month
- Also how we take on maintenance and small ongoing improvements
- Transparent reporting of what was done in the period
There are no prices on this page because “I need an online store” can mean two weeks or four months — the difference is in the integrations, the data and the deadline. That’s what the first conversation is for. Third-party costs (hosting, domains, paid APIs, licences) are billed to you by the provider, without markup.
What to send so the quote is fast
Send what you have. Missing items aren’t a problem — we’ll ask — but each one you include removes a round trip.
What the software has to do
The job it performs and who it performs it for, in your own words. If there’s a process being done by hand today, describe it — or record your screen doing it.
Who uses it
Customers, internal team, or both. Desktop or phone. Whether different people need different levels of access.
What exists today
The URL of your current site or store, what it’s built on, where it’s hosted, and whether you have access to the code and accounts.
What it must talk to
ERP, payment gateway, carriers, marketplaces, CRM, spreadsheets — names and versions, and whether they have a documented API.
Deadline and reason
A date attached to a reason — a campaign, a contract, a season — is something we can plan around.
Budget range
A range is enough. It doesn’t set the price — it tells us whether to propose the full build or a first version that solves the most expensive part of the problem first.
What we won’t take on
Where we say no upfront, so you don’t spend a week finding out.
Fixed price on an undefined scope
“We’ll work out the details as we go, but the price is closed” ends badly for both sides. Undefined scope gets hourly work or a scoping phase first.
Deadlines that skip the work
If a date can only be hit by dropping testing and staging, we’ll say no rather than deliver something that breaks in your checkout on the first sale day.
Quoting blind on inherited code
We don’t promise support on a codebase we’ve never opened. Reading it comes first, and then a real quote.
Mass messaging without consent
We build WhatsApp tools for stores messaging their own customers. We won’t build cold-contact blasters or scraped-list senders — it also risks the number your store depends on.
Work that breaks terms of service or the law
Scraping behind logins you don’t own, fake reviews, circumventing marketplace rules, or handling personal data in ways the LGPD doesn’t allow.
Fields we don’t work in day to day
Game development, crypto/token projects, and enterprise stacks outside our stack. A team that lives in them will build it better and cheaper.
Questions buyers actually ask
How long does a project take?
It depends on the scope, and we won’t pretend otherwise before the first conversation. What we commit to: the written scope includes a delivery estimate, and if something threatens it mid-project, you hear it from us early — not on the deadline.
Who owns the code?
The ownership terms are written in the proposal. Our default: code written specifically for your project is yours, delivered in a repository with full history. Open-source dependencies keep their own licences, and if one of our commercial plugins is part of the solution, it stays licensed — not sold.
What happens if requirements change mid-project?
Inside the agreed scope, we fix and adjust as part of the work. Outside it, the change is written down and quoted before it’s built — which protects your budget as much as our planning.
Can we hire you for maintenance only?
Yes. It starts with us reading the codebase — we don’t quote support on code we’ve never opened. After that, maintenance runs on the hourly or monthly model.
Do you work with clients outside Brazil?
Yes — the site, the products and our communication run in Portuguese and English. Raise currency and invoicing in the first message so we confirm the practical details before scoping.
How much does it cost?
We don’t publish prices because the honest answer depends on scope. What we can promise: a written quote after one conversation, a budget-range question that exists to size the proposal (not to inflate it), and third-party costs billed to you directly, without markup.
Can you work alongside our developer or agency?
Yes, with one condition: clear boundaries about who owns which part, agreed in writing before we start. Shared codebases without ownership boundaries are how projects stall.
Do you host what you build?
You can host it anywhere. If you want it handled, we set up infrastructure on Google Cloud or recommend managed WordPress hosting through our BoolHost partnership — accounts in your name either way.
Request a quote
Fill in what you know. You’ll get a reply from someone who works on the code — with questions, or with a proposed next step.
Prefer another channel? WhatsApp +55 41 98783-3020 or [email protected].
Related: Our plugins · WordPress hosting · Security and data protection