An innovation department is an unglamorous thing to put in a success story. It has reporting lines, assigned employees and meetings. Yet those are among the tangible results IEBT Innovation lists for its work with Sicoob Credicom, a Brazilian financial cooperative. Alongside an innovation management system, the consultancy reports a larger dedicated team and a structured program for employees to develop ideas. Someone, in other words, would have to show up on Monday and keep the work going.
That is a useful entry point into IEBT, a Brazilian company whose services range from corporate innovation consulting to software development and startup acceleration. Its business occupies the awkward territory between deciding that change is necessary and making change part of an organization’s routine. The interesting product is often the arrangement around the technology: who selects it, who builds it and who takes responsibility once the presentation ends.
The cooperative needed an operating system for ideas
Credicom faced an organizational problem as financial services became more digital. IEBT’s case account describes a conservative environment with low maturity in innovation management. The brief included creating a more experimental culture, linking innovation to strategy and establishing an innovation function. The reported outputs are therefore organizational: a management system, full-time staff, an employee entrepreneurship program and more than 20 external communication initiatives.
An earlier account describes the opening moves: an innovation maturity diagnosis and seminars, with consultants Mariana Santos, Thales Linke and Gustavo Nogueira involved. The company’s historical case material dates the engagement to August 2021 and describes an 18-month duration. That timescale is revealing. A cooperative buying this kind of work is committing to a sustained intervention in how people make decisions.
The practical lesson, as an editorial reading of the case, is to name the owner before celebrating the idea. A workshop can generate enthusiasm; an assigned team can decide which proposals deserve resources. A buyer could copy that sequence by assessing the existing process, assigning responsibility and giving staff a clear route for proposing experiments. Each step creates something that can be inspected after the consultants leave.
- 01 Diagnose maturity
- 02 Assign a team
- 03 Organize the work
- 04 Invite employee ideas
A laboratory background, with a commercial address
IEBT’s roots reach back to 2009 and a meeting of university research with business incubation. Its 17th-anniversary account says some founding partners came from a UFMG innovation research laboratory and others from an incubator. In 2012, the company moved into BH-TEC, Belo Horizonte’s technology park. Its name spells out an older description of the startup world: Instituto para o Desenvolvimento de Empresas de Base Tecnológica.
That lineage helps explain a portfolio that includes both research commercialization and corporate technology work. A profile submitted to FAPESP describes experience with research-intensive startups and acceleration programs, including SEED initiatives. It positions IEBT as an academic spin-off with familiarity in developing businesses around technical knowledge. For a research team, that is a different starting conversation from commissioning an ordinary website.
The company’s chosen symbol is smaller than its name. “Nossa logomarca é um pixel,” its anniversary article says: our logo is a pixel. The explanation is a metaphor for people contributing to a larger whole. It also suits a business whose deliverables come in many small pieces: interviews, requirements, technical decisions, evaluations and working code.
Zing gives the paperwork a home
Zing is IEBT’s own innovation management platform. Its earlier product site describes publishing programs, collecting proposals, assessing startups and managing proofs of concept. Acceleration tools include mentoring records, documents, workshops and activity tracking. For the organization running a program, the appeal is a shared record of what applicants submitted and what happened next. For startups, it provides a route into opportunities run by companies and public institutions.
The current offering puts public sector work prominently in view. Zing describes work for CAIXA’s TEIA, Cemig and Porto de Suape. Its Suape case covers preparation of an innovation contracting process; the CAIXA example includes platform customization and support for evaluating startup applications. These are jobs where the quality of the process matters alongside the quality of a proposal.
One figure puts the scale of a program in perspective. Zing reports R$7.6 million invested in 50 startups across nine municipalities through Espírito Santo’s Programa Sementes. That number belongs to the supported program. It should be read as startup investment, with the recipient attached, rather than used as a shortcut for the consultancy’s size.
A platform of this sort is most useful when many people need to work from the same information. The editorial implication is straightforward: use it when submissions, evaluations and follow-up have become a coordination problem. A small team considering two vendors may need a simpler process. Software brings structure, but the organization still has to decide what a good proposal looks like.
Industry needs someone to run the program
IEBT’s partnership with Brazil’s industrial development agency, ABDI, offers another view of the work. Startup Indústria seeks to connect industrial needs with innovative companies and experiments. ABDI describes IEBT as an operating partner providing methodology and technical and operational guidance. A contracting notice dated October 24, 2024 lists pairings of productive-sector companies and solution providers, including Bosch and UDEV.
The program’s application instructions require proponents to explain objectives and feasibility, and exclude identifying references from the proposal text. That is a small but telling detail. An innovation intermediary does more than introduce people at an event. It helps establish the conditions under which a proposal will be considered and the steps that follow selection.
The company also markets startup acceleration through Tecnova. Its landing page reports accreditation in 20 states and more than 1,300 businesses accelerated, figures presented by IEBT itself. The services include commercial advice, connections to investors and support for product development. Technology mentoring is a notable part of the pitch: founders can need help improving the way a development team works as much as refining a sales presentation.
The software team is part of the proposition
IEBT’s software offering gives its consulting business a practical second route. A client can seek help shaping an innovation program, or bring in people to build digital systems. The company advertises agile development squads alongside data science, analytics and automation. Its wider corporate services include roadmapping, innovation portfolios, open innovation and advice on corporate venture building and investment.
Commercially, this places IEBT across several buying decisions. An innovation executive may need program design. A technology leader may need delivery capacity. A public institution may need an operator for an initiative involving external companies. The business combines professional services and program operation with proprietary software. The exact engagement should follow the task: buying an assigned development team is a different commitment from adopting a platform.
A 2023 partnership with Lanum illustrates how IEBT adds specialist capability. The collaboration focused on conversational customer interactions and projects involving Blip. TI Inside’s account described a combination of Lanum’s conversational expertise with IEBT’s delivery capacity. It is an example of a technology consultancy using a partner to address a particular customer interface.
The alternatives therefore depend on the brief. Buyers can use their own innovation staff, commission a specialist accelerator, purchase program software or hire a development provider. IEBT’s distinguishing proposition is the combination. The buyer’s question is whether that combination reduces the work of coordinating suppliers for the specific project at hand.
“Nossa logomarca é um pixel.”IEBT Innovation · 17th-anniversary article
“Our logo is a pixel.”
AI inherits the same stubborn assignment
IEBT’s newer public positioning emphasizes AI, data and software engineering. Its anniversary account introduces Cognit AI, a proprietary platform of reusable technical assets and governance, and Chimera AI, its research and development laboratory. The company describes an effort to take AI from experimentation into corporate use. It is the latest version of a familiar assignment: make technical work useful inside an institution.
That transition asks more of a client than approving a demonstration. As a practical inference from the delivery model, someone must make data available, define the intended outcome and take ownership of ongoing use. Where those decisions are unresolved, adding technical capacity can leave the underlying decision untouched. The appropriate first purchase may be the work of defining the problem and its owner.
People management matters on the supplier’s side, too. Ricardo Almeida, identified in a company article as a co-founder and People Director, describes three retention priorities: the working environment, professional development and compensation. The article discusses feedback, training effectiveness and how employees experience individual projects. Those details matter to customers buying specialist time: continuity depends partly on whether the specialists want to stay.
A reader borrowing this approach could write a brief with four concrete requirements: a named internal owner, an agreed decision process, a record of the experiment and a plan for the next stage. These are editorial recommendations drawn from the cases, rather than a claim about a proprietary IEBT formula. They make the engagement easier to judge because each requirement leaves evidence that the buyer can review.
For software projects, that evidence might be a working feature accepted by the client. For an acceleration program, it might be a completed evaluation and a documented next step for a participant. The measurements should follow the job. Counting applications tells a different story from counting adopted solutions, just as a workshop attendance list tells little about whether employees can get an experiment approved.
IEBT’s most useful cases invite a modest test of innovation spending. Look for a changed process, an accountable team, a managed experiment or software someone actually uses. Then ask what the next decision will require. That is the work the Credicom example makes visible, and the thread connecting the company’s programs, platforms and engineering teams. The brainstorm gets the room talking. The assignment continues when everyone returns to their desks.