Hey Clief Notes fam! 👋 I’m Junmarvi from the Philippines, currently based in the UAE. I work in materials and operations in the EPC industry, with a Computer Science background. Over time, I’ve moved deeper into AI-directed engineering—designing and shipping production-ready systems, workflows, internal tools, and structured workspaces for agents, context, verification, and standards. My goal now is to keep expanding what I can build, connect with more serious builders, and create opportunities that will eventually allow me to return home to the Philippines and continue this work with my family. Right now, I’m focused on improving how I orchestrate AI across architecture, implementation, security, testing, deployment, and long-term maintainability—while building a stronger network around real-world AI engineering. .

I’m currently using AI to research ideas, organize projects, and help me build my business. Right now I’d say I’m at the building structured systems stage, but I’m still learning a lot as I go. One thing that caught my attention from this lesson is the idea of giving AI the right information for the specific job instead of throwing everything at it at once. I’m already using different AI tools for different jobs, and I want them to work together without everything getting confusing. I’m excited to learn how to build better systems and eventually have different AI agents handling the things they’re best at, like helping me research, find leads, stay organized, and take care of repetitive work. My goal is to save time, reduce the amount of stuff I have to manage manually, and build something that can eventually keep working even when I’m not sitting there telling it what to do.

I am running an ICM knowledge base for my engineering company using GitHub, VS Code, and Claude Code. The efficiency gains in our workflows have been massive, and I see a clear opportunity to offer this to other regional companies as a new business unit. ​However, this dev-centric stack creates too much friction to be presented directly as a product to non-technical clients. ​The model I envision starts with heavy consulting to align the client's processes and culture. Once maturity is reached, it transitions into a managed service: issue tracking, periodic context pruning, and ad-hoc consulting for new agentic features. ​Has anyone here successfully commercialized this philosophy? I am particularly interested in how you package the delivery and abstract the technical friction (like the IDE and repo management) for the end user. Are there platforms already solving this?

Shipped a few production features this week focused on security and observability. Our construction project management system now has: - Device detection — flags logins from different machines - Concurrent session control — automatically logs out duplicate sessions - Real-time error monitoring — captures issues and sends alerts through WhatsApp - Usage tracking — shows active users, session duration, and feature activity This is not a demo. It is deployed internally and handling real operational data. The main value so far: - Reduces credential sharing across teams - Helps catch problems before users report them - Shows which parts of the system people actually use Next: GPS integration for equipment tracking and delivery validation. What started as an internal operational tool is slowly becoming something that could potentially be productized. For those who have gone through this before: how did you approach the transition from internal software to something you could sell externally?

It’s live. Starting today, everyone in Clief Notes has access to the new Clief Notes AI. The easiest way to use it? Don’t overthink it. Ask it the question you would normally ask me. “Where should I start?” “What should I focus on next?” “Where did you talk about [topic]?” It’ll use what’s already inside Clief Notes to help answer you and point you toward the right lesson or resource when there’s something worth going deeper on. The goal isn’t to give you another AI tool to play with. It’s to make everything already inside this community easier to actually use. If you want Access to it Comment "READY" and we'll send you access to it!