Understand before building
The work starts with the process that already exists and the number you want to change. Tools come later, and only where they change that number.
About the founderSee LinkedIn profile
Lucas Palhares Barbosa
Founder of Weft Systems · Tech Lead & Software Engineer
A software engineer for 10 years, with a career built on critical systems in banking, telecom and healthcare: the kind of system that cannot stop and cannot fail.
He applies AI Engineering every day (agents, automation and specification-driven development) in real environments, with deadlines, teams and legacy systems. Weft's method was born from that practice, not from courses or theory.
He founded Weft Systems in 2026 to bring that standard to companies of any size: from the executive who needs to know where AI produces results to the business owner who still writes appointments in a notebook.
10 YEARSin software engineering
SECTORSBanking, telecom and healthcare
TODAYAI Engineering applied every day
BASESão José do Rio Preto (SP), Brazil
Why Weft
Not theory. Engineering that runs Monday to Friday.
Critical systems don't accept improvisation: banking, telecom and healthcare teach that early. Weft brings that standard to companies of any size, with one difference: what reaches you has already been tested in real environments, with deadlines, teams and legacy systems.
Prototype before developing
You approve a clickable prototype before a single line of production code exists. Changing your mind at that point costs an afternoon, not a month.
Measure after delivering
The success criterion is agreed in writing at the start and checked at the end. “The system was delivered” is not a result. The number is.
Want to know whether software or AI moves your number?
A 30-minute call, no corporate pitch.