OpenClaw Manila
Speaker · AWS Manila, Philippines
OpenClaw at AWS Manila / Speaking & AI implementation
Company-wide agentic AI implementation
I spoke at OpenClaw Manila, held at AWS Manila, about company-wide agentic AI, deep-research workflows, and the open-source movement: how teams can investigate a question, review the evidence, and adapt agent systems to their own work.
Nino Amor · Community talk
From a promising demo to a company workflow
At OpenClaw Manila, held at AWS Manila, I spoke about implementing agentic AI across a company. The focus was the operating work that turns an individual experiment into something a team can use and maintain.
That starts with choosing a real use case and defining the agent's responsibility. A team needs to know what the system should produce and when a person takes over.
Design the work around the agent
The talk connected use-case selection with workflow orchestration and human review. Shared context, clear handoffs, and an owner for the next step matter when the work moves beyond one person experimenting with a tool.
My perspective comes from building agent workflows alongside product, growth, and operating responsibilities. Implementation has to fit the way the company actually works.
Deep research that a team can use
Deep research is one of the workflows I care about most: turn an open-ended question into a clear brief, break it into smaller questions, gather relevant sources, and bring the findings together for review. The useful output is something another person can check and act on, with the evidence close to the claims.
For company work, that means carrying source links, conflicting findings, and unanswered questions into the handoff. An agent can help with research and synthesis; someone still needs to judge the evidence and decide what happens next. I connect that research work to product decisions, implementation planning, and the operating context behind the request.
Why the open-source movement matters to me
I’m interested in open-source AI because it gives builders more room to inspect how a system works, adapt it to a particular team, and learn from what other people are building. That matters when an implementation needs to fit existing tools and processes rather than stop at a standalone demo.
The freedom to adapt a system also brings maintenance work: dependencies, permissions, updates, and documentation need owners. My perspective comes from operating agents and local services as well as building products. I want teams to understand what they are running, where it depends on outside services, and how they will keep it useful.
Make adoption part of implementation
Company-wide capability needs more than access to an agent. People need a useful first workflow, documentation they can act on, and a way to review failures and improve the instructions.
That is the connection I emphasize in my speaking and consulting: the technical workflow and the operating habits around it need to be designed together.