Revenue and relationships
- CRM pipelines and follow-up rules
- Client portals
- Marketplaces
- Sales workflows
CUSTOM SOFTWARE
Software built around the way your business works.
We build client portals, internal tools and CRM workflows connected to the systems you already use. Start with one process your team can test and validate.
Scope, schedule and investment are agreed after diagnosis.
THE PROBLEM
Disconnected tools leave your team doing the same work twice.
We define the process the software needs to support, the deliverables and third-party dependencies. You know how each stage will be validated before implementation starts.
01
Spreadsheets used as the operation's primary record
02
CRM, ERP and service channels without a reliable shared workflow
03
Repeated tasks that depend on manual checks and handoffs
04
Business rules spread across people, spreadsheets and tools
05
Teams lose context when work moves between systems
06
An off-the-shelf tool covers part of the process but blocks the rest
SYSTEM TYPES
Build the parts your operation needs.
Start with a concrete journey. The technical design follows its owners, data and exceptions.
Operations and control
- Back offices
- Operational dashboards
- Permissions and approvals
- Process auditing
Data and integrations
- Integration layers
- Event-driven workflows
- Data consolidation
- Observability
PROJECT FIT
Start with a process your team can validate.
A good fit when
- Operations with a recurring process and clear impact on revenue, capacity or quality
- Businesses that already use systems and need to connect them without replacing everything at once
- Teams with an owner who can make decisions, validate the work and provide system access
- Projects that can start with a defined journey and acceptance criteria
A poor fit when
- Hourly developer allocation
- Open scope without an internal owner or clear priority
- Replacing an entire operation without diagnosis, access and a rollout decision
CUSTOM INTEGRATIONS
Connect the tools your business already uses.
We build the layer that connects APIs, webhooks, data and operating rules. Depth depends on each provider's access, permissions and limits.
Shopify
Nuvemshop
CRMs
ERPs
Payment gateways
Logistics
Internal systems
When a scope includes WhatsApp or agents, messaging and agent infrastructure is available. Syntesi builds the custom integrations with your systems and operating rules.
PROCESS
Each phase defines what is included, how we validate it and what comes later.
01
Diagnosis
Map the process, its owners, the systems involved and the risks of the first stage.
02
Workflow & metrics
Define the steps, exception handling, events to track and acceptance criteria.
03
Build
Deliver demonstrable increments with repository access and documented decisions.
04
Controlled rollout
Prepare the environment, permissions, required data and a gradual production release.
05
Measurement
Review events, failures and usage to see whether the workflow operates as agreed.
06
Evolution or handoff
Deliver documentation, prepare your team to continue and agree whether there will be another phase.
RELATED EXPERIENCE
Relevant individual experience.
PropTech
- Product
- Growth
PilarHomes
Lucas's professional experience
- Context
- A premium real estate marketplace within a PropTech operation.
- Problem
- The journey needed to preserve context and trust throughout property discovery, presentation and negotiation.
- Lucas's role
- RFC · Product · Frontend engineering · Production delivery
- Solution
- Property page and contextual navigation
- Curated collections with named curators
- Off-market flows
- Outcome
- A property discovery and presentation experience in production, preserving context throughout the journey.
- Scale
- Marketplace and real estate operations
- Reliability decisions
- Delivery from RFC to production
PropTech
- Platform
- AI
Catalog Integrity
Lucas's professional experience
- Context
- Internal operations for property quality and availability.
- Problem
- Unavailable or outdated properties created noise and recurring operational review.
- Lucas's role
- Engineering leadership · Architecture · Backend · Observability
- Solution
- Multiple-signal analysis
- Confidence-based rules
- Asynchronous workers
- Auditing and human review
- Outcome
- A catalog integrity operation combining automation, auditing and human review.
- Scale
- A continuously operated real estate catalog
- Reliability decisions
- Auditable restoration · Human review proportionate to risk
PropTech / SaaS
- Product
- Growth
- Platform
Superlógica
Lucas's professional experience
- Context
- An operations platform for condominium management and the real estate market.
- Problem
- Lead and search flows needed to become faster without disrupting the product in production.
- Lucas's role
- Analytics · Database · Frontend · Search · Web and mobile
- Solution
- Analytics-led improvements
- Frontend modernization
- Search improvements
- Outcome
- Lead, search and experience flows improved without interrupting the existing product.
- Scale
- A SaaS platform with web and mobile experiences
- Reliability decisions
- Incremental improvements · Continuity of the product in production
PROJECT PRICING
SCOPE AND INVESTMENT
We quote the work after diagnosis, based on the process, integrations, data and delivery requirements. The proposal lists deliverables, acceptance criteria, dependencies and responsibilities before development starts.
Focused pilot
Quoted after diagnosis
Schedule agreed in the proposal
Operational platform
Quoted after diagnosis
Schedule agreed in the proposal
AGREEMENTS AND HANDOFF
Scope, ownership and handoff agreed before delivery.
Project scope and milestones, acceptance criteria and responsibilities are agreed before delivery. The client receives the project code, subject to third-party licenses, and repository access as agreed.
COMMON QUESTIONS
Questions to answer before deciding.
Do you work for a fixed project fee?
Yes. We organize the project around deliverables, milestones and acceptance criteria. We assess significant scope changes before implementation.
Does the client own the code?
The client receives repository access and the code developed for the project, subject to disclosed third-party components and licenses.
Do you replace an existing CRM or ERP?
It depends on the bottleneck. Integrating, modernizing or adding an operational layer often solves the issue better than replacing an entire tool.
How do you handle third-party integrations?
We map APIs, webhooks, permissions, limits and responsibilities before agreeing on the scope. Provider and client access dependencies are listed in the proposal.
Can we start with one part of the operation?
Yes. A focused pilot addresses one defined journey and lets the team validate the integration, workflow and acceptance criteria before expanding the platform.
Do you continue after delivery?
We can agree on a managed evolution phase or finish with a documented handoff and repository access. The choice is explicit in the scope.
Do you guarantee operational results?
We agree on the contracted deliverables and acceptance criteria. Operational results also depend on data, adoption, internal decisions and third-party systems.
Next step
Which part of your operation needs better software?
Describe the process, the people involved and the systems you already use.
Discuss your project