Custom software
Software with your name on it, built from scratch.
Payload CMS portals, back offices, automations and SaaS MVPs. The same team that builds and runs Rota.Rank writes your system, ships it and hands over the code in your repository.
01 / Portals and blogs · Payload CMS
The new WordPress, with far more possibilities.
Payload is an open-source CMS written in TypeScript that runs inside Next.js itself. Instead of bending your content to a generic panel, we design the panel around your content and your team's workflow.
- Typed content: every field lives in code, with validation and autocomplete.
- Custom admin: collections, drafts, review and scheduling the way your newsroom works.
- Next.js and Postgres: front end and admin in one project, a real relational database.
- No third-party plugins: nothing breaks because an unknown author bumped a version.
- Performance and SEO: static or cached pages, metadata and sitemap in code.
- Multilingual and permissions: per-language fields and access by collection or field.
- App-ready API: REST and GraphQL generated from the same schema.
- Self-hosted: runs on your infrastructure, no per-seat license.
WordPress × Payload, no cheerleading
| Criterion | WordPress | Payload CMS |
|---|---|---|
| Content model | Posts and pages; extra fields via plugin | Collections and fields defined in TypeScript |
| Features | Thousands of ready-made plugins, each with its own update cycle | Written in your project, versioned and tested with it |
| Front end | PHP theme or headless via REST | Next.js in the same project as the admin |
| Speed | Depends on the theme and plugins: each adds PHP, CSS and JS to the page. Gets fast with caching, CDN and plugin pruning | Server-rendered or static HTML (Next.js SSG/ISR), only the JS the page uses, resized images in AVIF/WebP |
| Core Web Vitals | LCP, INP and CLS change with every new plugin; needs constant monitoring | Performance budget defined in the project and measured on every deploy |
| Technical SEO | Well served by plugins (Yoast, Rank Math), which also add weight to the page | Metadata, sitemap, canonical, hreflang and structured data generated in code from content fields |
| Permissions | Default roles; fine-grained rules via plugin | Rules per collection, document and field, in code |
| Getting started fast | Simpler: ready-made theme, cheap hosting, an editor everyone knows | Requires development before the first post goes live |
| When to choose | Blog or company site on a lean budget with a team already used to it | Portal with structured content, several languages, an app or access rules |
Real case · Rota dos Viajantes
View the caseSame site, same hosting. We only swapped WordPress for Payload.
WordPress was already optimized, with LiteSpeed Cache and Cloudflare, and still fell short. The Payload + Next.js version ships less than a fifth of the weight and almost no JavaScript blocking the screen. Speed is part of Google's page experience signals and matters even more for mobile visitors.
- Performance (mobile)
- WordPress: 20Payload: 87
- Performance (desktop)
- WordPress: 67Payload: 98
- Mobile LCP
- WordPress: 5.8 sPayload: 3.9 s
- Blocking time (TBT, mobile)
- WordPress: 1,895 msPayload: 47 ms
- Layout shift (CLS)
- WordPress: 0.40Payload: 0
- Page weight
- WordPress: 3.6 MBPayload: 0.65 MB
Lighthouse 12.2.1 (the engine behind PageSpeed Insights), median of 3 runs per version on 10/10/2026, rotadosviajantes.com.br home (WordPress) against the new version in staging (Payload). Both on Hostinger.
Staying on WordPress? That makes sense for many sites. For them we have Rota.WP, our WordPress plugin (affiliate links, blocks and metrics). We also migrate from WordPress to Payload when the time comes.
Discover Rota.WP02 / Back offices and internal systems
The whole operation on one screen, instead of scattered spreadsheets.
For companies that have outgrown spreadsheets and chat apps as their system. The team records, approves and tracks daily work in a panel built for its process, with a history of who did what.
- Juros BaixosInternal panel for financial operations, partners and routines: the team records, approves and tracks day-to-day work without scattered spreadsheets.case
- PreksBack office for product operations: internal flows, centralized data and a single view for whoever runs the platform.case
- Já ConteiEditorial and operational back office for content and SEO: publishing, organization and the routines of the people who keep the site running.case
All three in production today.
What usually goes in
- 01RecordsClients, partners, products and contracts with search and filters.
- 02Approval flowsSteps, owners and deadlines, with a notification at every change.
- 03FinanceEntries, reconciliation and payouts tied to the operation.
- 04PermissionsEach person sees and edits only what their role allows.
- 05ReportsOperational metrics and exports for whoever needs them.
- 06Audit trailHistory of who did what and when, on every record.
03 / Automations and integrations
Tools that talk to each other without anyone copying and pasting.
APIs, webhooks and scheduled jobs that remove repetitive manual work between ERP, CRM, payments, spreadsheets and AI models.
- A confirmed payment creates the order, invoice and email on its own
- Queue with retries when an external service goes down
- A log of every run and an alert when something fails
- APIs
- Webhooks
- Crons
- Queues
04 / SaaS MVPs
From idea to a product charging subscriptions.
The same foundation that runs Rota.Rank: portable architecture, ready to grow without a rewrite when the first customers arrive.
- Accounts and login
- Stripe subscriptions
- Customer dashboard
- Internal admin
- Transactional email
- Three languages
Other things we build
- Members area
- Customer portal
- AI assistant over your documents
- Data dashboards
- WordPress → Payload migration
- APIs for apps
- Custom WordPress plugins
05 / How to hire us
Fixed scope or a monthly team. You choose after discovery.
- 01Discovery
- 02Technical scope
- 03Biweekly deliveries
- 04Operation and evolution
- Code in your repository, in your organization, from the first commit
- Deploy on your infrastructure, with backups and monitoring
- Documentation technical and user docs for the team
- Support after delivery, agreed in the scope
06 / FAQ
What people ask before we start.
Still have a question? Talk to us.
How long does a project take?
It depends on the scope, which is why we start with discovery. At the end you get a schedule of biweekly deliveries with a date for each.
Who owns the code?
You do. The repository lives in your company's organization from the first commit, and the code, data and infrastructure accounts are yours. If you ever want to continue with another team, they start from the same repository and documentation.
Where is the system hosted?
On your infrastructure, with a provider that fits the volume and budget. We set up automated deploys, a managed database, backups and monitoring, and keep the access under your company's name.
Who maintains it after delivery?
Your choice: continue with a monthly squad, hire support for fixes and updates, or take over with your own team using the documentation we deliver.
Can you migrate my WordPress site to Payload?
Yes. We map posts, pages, categories, authors and media to typed collections and keep the URLs or add 301 redirects so you don't lose Google rankings. If WordPress still serves you well, we'll say so, and Rota.WP may be the way.
How much does it cost?
On request. The price comes out of discovery, together with scope and timeline, for a fixed scope or a monthly squad.
What about the contract and data protection (LGPD)?
We work with a services agreement and, when the system handles personal data, a data processing agreement. We follow the LGPD in code: consent, defined retention, permission-based access and an audit trail.
Tell us the problem. We reply with a technical scope.
No sales deck: you get a reply with the next steps.