Map the process
Identify who does what, which data is needed, who approves it and what counts as completion.
What would you like to explore?
Wisnu Falah / Batam / Corporate portfolio
Wisnu Falah
Building systems around how a business works.
From everyday work to management decisions. I am building INDOWYSS to connect records, workflows and evidence-based recommendations; the same approach can be developed around your company's needs.
Founder & product builder, INDOWYSS
01 / Work in practice
See the system. Follow the thinking.
INDOWYSS is my main project: one ecosystem connecting operations, an automated Manager, cross-business promotions and collective purchasing. These are selected workflows that have been built.
Work in practice
Work priorities
Not another dashboard. A clearer next action.
Today brings operational issues to the owner's attention. Business Plans separate pricing, equipment and staffing decisions from everyday tasks.
- Issues, evidence and actions in one workflow.
- Separate places for daily work and medium-term decisions.
Decisions & costs
Check the numbers before adding a cost.
Simulations combine business records with owner-entered assumptions to compare additional costs with the sales needed to cover them. Assumptions remain distinct from observed results.
- Calculations can be checked; AI does not invent the figures.
- Important changes remain subject to human decisions.
Review results
The workflow continues after a recommendation.
Recorded trials can be reviewed after 7, 14 or 28 days. INDOWYSS compares before-and-after records and explains the observed changes.
- Examples of both improved and declining results.
- A comparison alone does not prove causation or net profit.
02 / My contribution
From understanding the work to testing the result.
Build the working experience
Connect forms, statuses, priorities and permissions, with interfaces adapted for phones and computers.
Connect data & decisions
Validate inputs, calculate indicators, explain evidence and prepare next steps. Use AI where appropriate, without replacing controls.
Test workflows & risks
Test scenarios, repeated requests, concurrent changes and access restrictions. Start a rollout with a scope that can be verified.
I connect business context with system delivery.
I develop INDOWYSS independently, using AI assistance for code, documentation and testing. My contribution spans requirements mapping, workflow and interface design, rule definition, implementation coordination and result verification.
Direct experience in retail, sales and F&B helps me understand the people doing the work. INDOWYSS began with a manual-recording pilot for small F&B businesses in Batam and developed into a digital system.
Technical foundation & AI approach
Application & data
The INDOWYSS foundation uses TypeScript, Next.js/React, NestJS, PostgreSQL and Prisma. Recording, calculations and presentation are separated so they can be tested.
An engine before an explanation
Incoming data is validated, calculated and filtered by evidence and priority. External AI is prepared as an explanation aid, not a source of figures or an autonomous authority over money and decisions.
Delivery evidence
Transaction scenarios, access boundaries, calculations and interface workflows are part of testing. A focused demonstration and test summary can be discussed without exposing private code or internal data.
03 / Application to your company
Start with the process that holds work back.
An ERP, CRM or internal application need not start by replacing every system. These are examples of scopes that can be designed around a company's needs, not claims of deployed enterprise modules.
Inventory & purchasing
Connect item requests, approvals, receiving and price history.
Measure: processing time and inventory-record accuracy.
Sales & customers
Clarify lead ownership, follow-ups, visits and quotation status.
Measure: timely follow-ups and complete lead statuses.
Work & approvals
Track tasks, owners, deadlines and completion evidence.
Measure: overdue work and approval waiting time.
Management control center
Bring together priorities, exceptions and process summaries linked to source records.
Measure: report preparation time and clarity of follow-up actions.
Scope & integration
Integration with an existing ERP, migration, security, service costs and support are scoped after reviewing requirements and technical access. Machine-safety systems and industry-specific compliance require separate expertise and validation.
04 / How to begin
Clear scope. Test first. Then expand.
Choose the problem
Map the current process, users, bottlenecks and agreed success measures.
Prove one workflow
Build a usable example, then test it with users and approved data.
Handover & review
Agree on acceptance tests, guidance, access permissions, data recovery and support before a wider rollout.
Let's talk
A role to discuss, or a system to build?
Recruitment
For hiring teams
I am open to roles connecting operations and technology: process analysis, business-application implementation, product development or workflow testing. INDOWYSS demonstrates how I work.
Discuss a roleProject partnership
For company projects
Describe one process you want to improve. We can discuss an internal application or custom ERP/CRM module, from user requirements to scope, testing, costs and support.
Discuss a system project