Improving with kawak®

cordial greetings. Dear development team, First of all, I want to congratulate them for the excellent work they are doing with the software. It's a fantastic tool that brings a lot of value to the community. I've been closely following recent updates and wanted to share with you a constructive suggestion regarding the development ecosystem: keep access to the API for free, instead of implementing a charging model. Allowing the API to be free offers great strategic advantages for software growth: • Encourages innovation: Independent developers can create add-ons, integrations and secondary tools that enrich their own product without economic barriers. • Community growth: Open APIs attract a larger and more active user base, generating organic advertising and consolidating the presence of the software in the market. • Network effect: The more applications connected to your system, the more indispensable your core software becomes for end users. If financial sustainability is a concern, there are viable alternatives before closing the API behind a paywall: • Freemium models: Maintain a generous free tier for developers and charge only companies with an extremely high volume of requests (fee per use). • Monetization of the main software: Leave the API free as a hook to attract customers to the payment plans of the main application. Many of the most successful software on the market grew because they allowed developers to freely experiment with their data and tools. I hope you will consider this perspective to continue building together a solid and accessible platform. Thank you very much for your time, attention and for listening to your community. Sincerely, José David Garay Manager: Maken

Dear KAWAK team, Along with greeting, and in relation to the response provided to the previously reported incident regarding the API integration of the Continuous Improvement module, I would like to formalize this request as a requirement for improvement. Currently, when using the API to consume reports: * R1 — Improvement Opportunities Report * R2 — Action Plan Report there is a difference in the number of columns available compared to the platform's internal reports: * R1: 38 columns in the report vs 32 columns via API * R2: 31 columns in the report vs 27 columns via API As indicated by your team, this difference corresponds to a limitation of the current scope of the endpoint, which is not configurable from the client side. Since this restriction directly impacts the analysis and development processes of data analytics solutions in FALP, we formally request the evaluation and incorporation of the missing fields in the API, so that there is consistency between the information available in the reports and that exposed through integration. Objective of the improvement: Allow the API of the Continuous Improvement module to make available all the columns present in the R1 and R2 reports. I would appreciate it if you could consider this requirement within the development roadmap and, if possible, share an evaluation or implementation estimate. I look forward to any additional information you require to support the management of this request. Kind regards, Leonardo Thomson

Create a kawak® connector for PowerBI, which allows you to easily connect the kawak® API for report generation.