Revenue and customer service
- Assign leads with context in the CRM
- Follow up after a stage or proposal changes
- Hand off service conversations with a summary and owner
- Update orders and status for the customer
WORKFLOW AUTOMATION
Connect the work between your systems.
Connect lead follow-up, document review and operational updates across CRM, email, messaging and internal tools. Define the rules, approvals and exceptions before automating.
Scope, schedule and investment are agreed after diagnosis.
WHERE WORK GETS STUCK
Put the process rules where your team can follow them.
Before automating, we define who starts the workflow, what data it needs, who handles exceptions and which system records the outcome.
01
Data copied between CRM, ERP, spreadsheets and documents
02
Approvals chased through messages without a clear owner or deadline
03
Manual checks before orders, records or payments can move forward
04
Business rules spread across people and tools
05
Exceptions disappear when an integration fails
06
Recurring processes without a record of what happened
WORKFLOW EXAMPLES
Start with a familiar, repeatable process.
Operations and documents
- Validate records between a form and internal system
- Route document approvals with deadlines and owners
- Generate files from approved data
- Send exceptions to a team review queue
Finance and controls
- Reconcile billing and payment events
- Request approval above an agreed limit
- Record transactions in an ERP or spreadsheet
- Flag outstanding items and operating discrepancies
WORKFLOW ARCHITECTURE
Track inputs, actions, approvals and exceptions.
01
Input
An event, form, file or change in a system starts the workflow.
02
Validation
Check data, permissions and conditions before continuing.
03
Rules
Apply the business decisions documented in the scope.
04
Action
Create, update, notify or record in the right system.
05
Exception
Cases outside the rules return to a person with the relevant context.
06
Observability
Records show the state of each step, and alerts show when the workflow needs attention.
PROJECT FIT
The scope works when your operation can make decisions and handle exceptions.
A good fit when
- A recurring process with defined owners, rules and outcomes
- An operation that needs connected systems without replacing the entire stack
- A team with system access and time to validate the scope
- A journey that can start with a clear volume and exception limit
A poor fit when
- A process without a defined owner or rule
- Automation without the necessary API, data or permissions access
- A project that requires replacing the whole operation before testing a scope
- Open-ended hourly development
CUSTOM INTEGRATIONS
Connect the systems that still depend on manual handoffs.
We build the layer that connects APIs, webhooks, data, documents and operating rules. Depth depends on each provider's access, permissions and limits.
Shopify
Nuvemshop
CRMs
ERPs
Billing and payments
Spreadsheets and documents
Internal systems
When a workflow includes WhatsApp or agents, messaging and agent infrastructure is available. Syntesi builds the APIs, business rules and integrations with your operating systems.
GOVERNANCE
Decide what runs automatically and what needs approval.
Idempotency
The same event should not create a duplicate action.
Retries
Retry temporary failures within the agreed attempt limit.
Audit trail
Record the data received, decisions made and actions taken at each step.
Human approval
Risky or out-of-policy cases wait for a team decision.
Least privilege
Each integration receives only the access the scope requires.
MEASUREMENT
Measure the process before claiming an improvement.
These measures show whether the workflow runs as agreed. The project does not promise savings or revenue, which depend on the operation, data and client decisions.
- Cycle time
- Manual touches per case
- Error and rework rate
- Volume processed
- Exceptions returned to the team
PROCESS
Define scope, risk and acceptance criteria.
01
Diagnosis
Map the journey, systems, owners and risks.
02
Workflow & metrics
Define events, rules, exceptions, acceptance and measures.
03
Build
Build integrations, rules and records in demonstrable increments.
04
Controlled rollout
Launch a controlled scope with appropriate supervision.
05
Measurement
Review workflow execution, failures and exceptions.
06
Evolution or handoff
Deliver documentation and agree whether work continues in a separate 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
Your team needs to maintain and review the work delivered.
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.
Where do we start?
Start with a recurring process, an owner, defined systems and a clear decision about what should happen when the workflow fails.
Do you work for a fixed project fee?
Yes. We organize the project around deliverables, milestones, dependencies and acceptance criteria. We assess significant scope changes before implementation.
Can you connect our existing systems?
Yes, when APIs, webhooks, permissions and data support the agreed scope. Provider limits are listed in the proposal.
How do you handle exceptions?
We define which cases can continue automatically and which return to a person with the context needed to decide.
What is ready-made and what is custom?
When a workflow includes WhatsApp or agents, messaging and agent infrastructure is available. Syntesi builds the APIs, business rules and integrations with your operating systems.
Does the client receive the code and documentation?
Yes. The client receives the project code and documentation, subject to disclosed third-party components and licenses.
Do you guarantee savings or revenue?
No. We agree on deliverables and acceptance criteria. Savings and revenue depend on adoption, volume, data, internal decisions and third-party systems.
Next step
Which process still depends on manual follow-up?
Share the steps, systems and exceptions. We will assess what to automate first and where review is needed.
Discuss your project