Graduating Entrepreneurship student at De La Salle Lipa

Daniel Rodriguez
Business Automation & Systems Builder
I build practical business systems around real operational problems.

I focus on business automation, internal systems and reporting tools. I build around real workflows so repetitive work becomes easier to manage, accountability stays clear and management gets better visibility into what is happening.

What I build
Workflow automation, internal business systems, reporting tools and financial control workflows.
Featured build
BrightSmile Clinic Operations System with a live portfolio demo and complete case study.
Daniel Rodriguez, monochrome studio portrait.

What I do

Systems built around how the business actually works.

The problems I focus on usually come from repetitive work, disconnected records, unclear accountability or information that takes too much manual effort to prepare. I look at the workflow first, then decide where a better system can actually help.

  • Repetitive manual encoding that has to be entered again somewhere else.
  • Forms, messages, notes and spreadsheets that are difficult to connect.
  • Unclear accountability for who recorded something and when.
  • Reports that require people to rebuild information after the work already happened.
  • Management information that becomes useful only after too much time has passed.
  • Business data that already exists but is difficult to review or act on.
  • Workflow automation

    Turn repetitive operational steps into structured workflows so the same work does not need to be entered repeatedly.

  • Internal business systems

    Build practical tools for staff encoding, tracking, approvals and operational control.

  • Reporting and management visibility

    Turn operational records into reporting and management views that are easier to review and understand.

  • AI assisted automation

    Use AI when it genuinely improves a workflow, such as structured extraction, drafting or assisted processing. AI should solve a useful problem, not simply become a label on the product.

Featured work

BrightSmile Clinic Operations System

A mobile first clinic finance and operations system built around transaction accountability, financial reporting and reconciliation.

Daily Cashflow screen in the BrightSmile demo, showing summary cards for Clinic Sales, Other Revenue, HMO, Xray, Total Sales, Cash Expenses, GCash Expenses, Clinic Total Expenses and Xray Expenses.
Financial reporting in the running demo. All names and figures shown are synthetic demonstration data.

Portfolio demo · Synthetic data

  • Accountability
  • Financial control
  • Operational visibility
  • Mobile staff workflow. Staff can record operational transactions from a phone using a structured form designed around the information the business needs to keep.
  • Receipt supported records. Supporting receipts can remain attached to the transaction they belong to.
  • User and activity traceability. Recorded actions preserve the user, time and transaction detail so management can trace what happened.
  • Financial reporting. Operational records feed financial summaries without requiring the same transaction to be manually encoded again for reporting.
  • Reconciliation and variance detection. Expected and counted balances can be compared so days that need investigation are easier to identify.

BrightSmile Dental Center is a fictional clinic. The live demo is an isolated portfolio environment running on synthetic data. Every name, amount, supplier and record was generated for demonstration. It is not a client deployment, and no client results, performance metrics or ROI figures are claimed.

Approach

How I approach a business problem.

I do not start by asking what software should be built. I start by understanding how the work currently happens, where the friction is and what the business actually needs to control.

  1. Understand the workflow

    Who does what, in what order and what information each step depends on.

  2. Find the friction

    Identify where work is repeated, delayed, manually rebuilt or difficult to trace.

  3. Define what matters

    Decide what needs to be recorded, checked, attributable and visible to management.

  4. Build the system

    Create the smallest useful system that can carry the workflow properly.

  5. Test the real workflow

    Check normal use, corrections, late entries, errors and exceptions.

  6. Improve from evidence

    Use actual records and real usage to decide what should be improved next.

The goal is not to automate everything

The goal is to automate the parts that reduce repetitive work, preserve accountability or improve management visibility. Some processes are better left simple.

Why trust the work

Built on real operational problems and working software.

  • Built from a real operation

    My first systems came from actual finance and reporting workflows inside a family dental clinic. That gave me a real environment where I could observe the process, build around it and improve the system based on actual use.

  • Working software, not just mockups

    BrightSmile includes a live interactive portfolio demo, transaction records, audit activity, financial reporting, reconciliation and a complete walkthrough.

  • Tested beyond normal use

    The work includes input validation, failure handling, responsive testing, workflow verification and safeguards for situations where something does not go as planned.

  • Business and technical thinking

    My Entrepreneurship background helps me start with the business problem. Building the software lets me carry that thinking into an actual working system.

About

I am building my career from real problems, not sample projects.

I am Daniel Rodriguez, a graduating Entrepreneurship student at De La Salle Lipa focused on practical business automation and internal systems.

I started by building tools around real dental clinic operations, including expense recording, audit logging, financial reporting and daily reconciliation. That experience pushed me to learn more about workflow automation, software development, reporting systems and practical uses of AI.

I prefer building working systems around real problems instead of filling a portfolio with concepts that were never used.

I approach both sides of the same question: what does the business need to control, and what does the software need to do to support it?

Focus
Business automation and internal systems
Background
Entrepreneurship at De La Salle Lipa with hands on software implementation
Working style
Understand the workflow first, then build the system around it

Toolkit

What I work with.

I choose tools based on what the workflow needs.

Systems and automation

  • Google Apps Script
  • APIs and webhooks
  • Workflow automation
  • Structured data workflows
  • Notification integrations

Web and software

  • JavaScript
  • HTML and CSS
  • Responsive interfaces
  • Progressive web apps
  • Backend automation

Data and reporting

  • Google Sheets integrations
  • Dashboards and summary views
  • Financial and control reporting
  • Reconciliation logic
  • Audit logging

AI

  • LLM assisted workflows
  • Structured outputs
  • AI assisted development
  • Automation integration

Contact

Have a workflow that feels more manual than it should?

Tell me how your team currently handles the process. What gets entered manually? What gets checked? What information does management need but struggle to see clearly?

I can help look at the workflow and identify whether a better system, automation or reporting process could make it easier to manage.

danieljude.ro@gmail.com