Backend, payments, and reliable architecture for products that cannot fail in production.

Avoid missed payments, missed events, and billing issues — with a platform built to scale.

Most requested

Pix and card payment integration for SaaS

I implement payment flows with Stripe, Asaas, or an internal gateway, focused on checkout, payment confirmation, reconciliation, and operational security.

Best for

SaaS products in launch phase
Platforms that need to charge with Pix and card
Products with manual operations or fragile billing flows

What's included

Integration with Stripe, Asaas, or multi-gateway architecture
Endpoints and business rules for charging and confirmation
Core webhooks for successful payments, failures, refunds, and chargebacks
Persistence model and minimal audit trail
Technical documentation for operation growth

Format: Fixed-scope sprint

Average timeline: 3-7 days

Investment: from US$ 300

Expected outcome: You get a production-ready billing foundation, reducing operational failures and accelerating go-live.

High pain / high value

Reliable webhooks sprint

I structure resilient pipelines for critical events, avoiding loss, duplication, and inconsistent webhook processing.

Best for

SaaS that depends on payment events
Systems with intermittent integration failures
Products that have already suffered from lost events in production

What's included

Asynchronous queue to decouple processing
Retry with exponential backoff
Dead-letter queue (DLQ) for problematic events
Idempotency and duplication safeguards
Structured logs and a basic operations runbook

Format: Fixed-scope sprint

Average timeline: 3-7 days

Investment: from US$ 300

Expected outcome: Your system starts handling critical events with predictability, observability, and far less production fragility.

MRR-ready

Recurring subscriptions and billing implementation

I design and implement the billing foundation for recurring plans, upgrades, downgrades, renewals, payment failures, and subscription lifecycle events.

Best for

SaaS with recurring monetization
Products moving from one-time pricing to subscriptions
Teams needing a stable billing foundation

What's included

Plan, subscription, and customer status flows
Billing events and access updates
Payment failure handling and basic dunning
Subscription state modeling
Integration ready for future product evolution

Format: Fixed-scope project

Average timeline: 1-2 weeks

Investment: from US$ 500

Expected outcome: You gain a more reliable billing layer to grow recurring revenue without unnecessary technical debt.

Solid foundation

Backend architecture for growing products

I organize Node.js/NestJS backends with focus on modularization, use cases, separation of concerns, and sustainable scalability.

Best for

Projects that grew fast and lost structure
Teams with hard-to-evolve backends
Products that need a more predictable foundation

What's included

Restructuring with DDD, Clean Architecture, or Hexagonal
Domain and use-case boundaries
Pattern definitions for new modules
Maintenance- and evolution-oriented refactoring
Technical direction so the team can continue safely

Format: Fixed-scope project

Average timeline: 1-2 weeks

Investment: from US$ 700

Expected outcome: Your backend becomes clearer, easier to maintain, and better prepared to scale without becoming a bottleneck.

Production

Observability and incident prevention

I set up minimum viable observability so you can identify errors faster, understand production impact, and reduce response time.

Best for

Teams that discover bugs too late
Systems without operational traceability
Products where errors become manual support work

What's included

Sentry integration
Contextual structured logs
Standardized error handling
Alerts and minimum debugging trail
Best practices for production environments

Format: Fixed-scope sprint

Average timeline: 3-5 days

Investment: from US$ 300

Expected outcome: You gain visibility into production behavior and spend less time firefighting blindly.

Reliability

Automated tests for critical areas

I implement test coverage in your most sensitive flows to reduce regressions and increase delivery confidence.

Best for

Backends with deployment fear
Financial or critical flows without coverage
Teams with recurring production bugs

What's included

Unit and E2E test structure with Jest
Coverage focused on critical business flows
Builders, stubs, and mocks patterns
Improved deployment confidence
Foundation for continuous team evolution

Format: Fixed-scope sprint

Average timeline: 4-7 days

Investment: from US$ 350

Expected outcome: Your team gains confidence to evolve the product without breaking what matters most.

How it works

I prefer clear scopes and objective deliveries. This reduces risk, accelerates execution, and improves technical decision quality.

1. Quick diagnosis

I understand product context, main pain point, current risks, and business impact.

2. Fixed scope

We define an objective delivery with clear priorities, timeline, and aligned technical expectations.

3. Implementation

I execute the solution focused on code quality, predictability, and real production environments.

4. Clear handoff

I deliver documentation, guidance, and next steps so the team can maintain and evolve safely.

Problems I usually solve

You lose revenue because payments fail and no one quickly finds the root cause

Critical webhooks arrive duplicated, out of order, or get lost — forcing manual rework

Recurring billing breaks growth because the model is fragile and hard to evolve

Your backend keeps growing, but architecture debt starts slowing every delivery

Every deployment feels risky because critical flows can break without warning

Production incidents keep happening without enough context to debug fast

Frequently asked questions

Do you work only with fixed-scope projects?

Today, I prefer well-defined scopes or technical sprints with a clear objective. This increases predictability and reduces noise for both sides.

Do you only work with companies in Brazil?

No. I can work with Brazilian or international companies, especially in backend, payments, and architecture projects for SaaS.

Do you also take ongoing maintenance work?

Yes, in some cases. I usually start with a sprint or initial implementation and, if it makes sense, we evolve to continuous support or technical follow-up.

How much does a project cost?

It depends on scope, but I usually start with technical sprints between US$ 200 and US$ 800, after a quick diagnosis.

Which stack do you use most often?

Mainly Node.js, TypeScript, NestJS, PostgreSQL, Redis, AWS, SQS, Stripe, Asaas, Jest, and Sentry.

Backend, payments, and reliable architecture for products that cannot fail in production.

Most requestedPix and card payment integration for SaaS

Pix and card payment integration for SaaS

High pain / high valueReliable webhooks sprint

Reliable webhooks sprint

MRR-readyRecurring subscriptions and billing implementation

Recurring subscriptions and billing implementation

Solid foundationBackend architecture for growing products

Backend architecture for growing products

ProductionObservability and incident prevention

Observability and incident prevention

ReliabilityAutomated tests for critical areas

Automated tests for critical areas

Pix and card payment integration for SaaS

Best for

What's included

Reliable webhooks sprint

Best for

What's included

Recurring subscriptions and billing implementation

Best for

What's included

Backend architecture for growing products

Best for

What's included

Observability and incident prevention

Best for

What's included

Automated tests for critical areas

Best for

What's included

How it works

1. Quick diagnosis

2. Fixed scope

3. Implementation

4. Clear handoff

Problems I usually solve

Frequently asked questions

Do you work only with fixed-scope projects?

Do you only work with companies in Brazil?

Do you also take ongoing maintenance work?

How much does a project cost?

Which stack do you use most often?