The spreadsheet only one person understands
Fourteen tabs, inherited formulas, three versions in email. When that person goes on vacation, the operation stalls.
→ Internal solution
Software engineering · straight from the builder
Software when it makes sense.Results, always.
Synko finds where your operation loses time and only builds software when it is the simplest way out. The person who understands the problem is the person who puts the solution into production.
No proposal on the first contact.
Tic Task: hour logging integrated between Taskweb and Senior, from minutes to seconds per person.
Order routine
StepBeforeNow
Export orders from the ERPManualAutomatic
Paste into the shipping sheetManualRemoved
Check mismatchesLine by lineExceptions only
Notify shippingWhatsAppAlert
Recommendation: connect the ERP and the spreadsheet. No new system.
01 — Does this happen here?
Do you recognize any of these Mondays?
Each sign points to a different intervention. Not all of them are software, and Synko tells you which is which.
Copy from one system, paste into the other
Someone reconciles by hand what the ERP and the spreadsheet should exchange on their own. Every day, with a risk of error on every line.
→ Integration
The routine that eats Friday
Same report, same checks, every week. Stable enough to automate? Only worth it if the return justifies it.
→ Automation
The problem already has a name
The diagnosis exists. What is missing is someone to design, build and put the solution into production without losing context along the way.
→ Direct execution
02 — Not every problem needs software
Before quoting, Synko asks whether it is worth building.
Four questions decide the intervention. Half of the outcomes do not end in software, and that is a good diagnosis too.
- Outcome without software
- Outcome with software
Answer to see where to start.
I have a process that is causing trouble.
Is the process understood?
Improve the process first
Map the real flow before touching any tool.
Take this to Jean (opens in a new tab)Does it happen often and cost a lot?
Leave it for now
Measure first. The intervention would cost more than the problem.
Take this to Jean (opens in a new tab)Is the current tool the problem?
Make better use of what you have
Configure, train, adjust. No new system.
Take this to Jean (opens in a new tab)Where is the gap?
Between systems
Your systems start exchanging data on their own.
Take this to Jean (opens in a new tab)03 — Where to start
Almost every project starts small.
Entry point
Operational diagnosis
“Where are my bottlenecks?”
A conversation with the people who do the work, a map of the real flow and a prioritised recommendation. The recommendation may be “you don’t need software”, and that is a result too.
02
Custom internal solution
When the spreadsheet became the bottleneck
A tool designed for the real process, with the rules no off-the-shelf product covers. The code and access stay with your company.
03
Systems integration
Data stuck between systems
Systems that don’t talk start exchanging data on their own, with error logging and reprocessing. No more re-typing.
04
Routine automation
The task that eats hours
Stable, frequent routines, automated with logs and alerts. Nothing runs in the dark.
05
Deployment and stabilisation
“They built it, but it doesn’t run smoothly”
Putting the solution into the real operation, fixing what use reveals and making sure people adopt the tool.
The person who understands the problem is the person who puts the solution into production. From diagnosis to rollout, the same person, with no handoff and no middleman.
04 — When it is worth building
From problem to production, with the same engineer.
Every project has a beginning, a middle and an end. What was contracted is delivered, validated and accepted. Future evolution becomes new work.
Understanding
Problem, context, impact and success criteria.
Definition
Scope, solution, priorities and project limits.
Development
Building, with validation along the way.
Deployment
The solution starts working in the real operation.
Stabilisation
Fixes and follow-up under the agreed terms.
Acceptance
Delivered, validated and accepted. The project ends here.
05 — The solution is yours
If Synko disappears tomorrow, your operation keeps running.
Synko builds on its own infrastructure and, at acceptance, hands everything over to your company: code, data and access. Nothing stays tied to an account or password only Synko holds. Maintenance and evolution stay available, if you want them.
“My work ends well when the solution keeps running without me.”
Synko
After acceptance, nothing is held back here.
Support: only if you want it
Your company
Everything that keeps the solution alive.
- Source code
- Data
- Access and passwords
- Documentation
One point of contact
Synko touches your operation to build. Ownership stays on your side of the line.
06 — Who builds
Six real problems, solved by the same person who will work with you.
I'm Jean Diego, a software engineer in Itajaí (SC), Brazil. I work with healthcare, banking, fintech and real estate systems. Through Synko, I work with companies directly: you talk to me from diagnosis to rollout, with no account manager in between.
- 01−98%
Login renewal errors on a healthcare platform built on microfrontends. Requests dropped 58%, about 3.8 million fewer per month, and the production identity service now takes less load.
Dasa · NAV Healthcare* - 0230 → 4 min
Salespeople waited up to 30 minutes for the app to sync after login. It dropped to 2 to 4 minutes, with a safe way back if the source system failed.
Plaenge* - 036 months
A discontinued offline first app became a web and PWA version, with two months set aside just to validate commercial calculations. With no sync to wait for, login now takes up to 500 ms and critical screens got about 80% faster.
Plaenge* - 04−32%
Load time of the investment funds page, on a platform with over 500 thousand users.
Avenue* - 05min → s
Daily hour logging integrated between Taskweb and Senior. What took minutes per person now takes seconds.
Tic Task - 060 → prod.
CF Diesel swapped hand-edited PDFs for an app for quotes, service orders and PDFs. Delivered from zero to production, it is in use and the client is satisfied.
CF Diesel
* Jean Diego's professional experience as an engineer. Not Synko clients.
Frequently asked questions
What people usually ask before the first conversation.
How much does a diagnosis or a project cost?
There is no price list. Every case has its own particularities and complexity, and is assessed individually. What I can say is that I price by delivery, not by hours worked.
How long does it take?
It depends on the process. The timeline is set in the conversation, case by case, before any commitment.
Do I need to understand technology to talk to you?
No. You describe the process that is giving you trouble and I talk to the people who run the routine. The technical part is on me.
What if my problem is not a software problem?
I will say so. The outcome can be improving the process, making better use of what you already have, or leaving it alone for now. I only build software when it is the simplest way out.
Do the code and data stay with my company?
Yes. At acceptance, the code, data, access and documentation are transferred to your company. Nothing is tied to an account only Synko holds.
Why one engineer instead of an agency?
Because the person who understands the problem is the person who puts the solution into production. You talk to me from diagnosis to rollout, with no account manager and no handoffs.
What happens after acceptance?
The project ends with the delivery validated and accepted. Maintenance and evolution remain available if you want them, and future evolution becomes new work.
Do you work with companies outside Santa Catarina?
Yes. Synko is based in Itajaí (SC) and serves all of Brazil.
Contact
Tell me about the process that's giving you trouble. If it's not a software problem, I'll say so.
No proposal on first contact. The conversation is about the process, and the outcome may be to build, adjust or leave it as it is.
Contact
No proposal on first contact. The conversation is about the process, and the outcome may be to build, adjust or leave it as it is.