Rifki Rosada | Personal Product

Spectre Insight

AI-first web product that turns uploaded spreadsheets into concise management briefs using LLM parsing.

Solo Founder & Engineer Ongoing — early access live Public product build
  • Problem

    Operators and managers regularly receive raw spreadsheet exports (sales, ops, inventory, performance) that take hours to manually parse into something a leadership team can act on.

  • My scope

    Built the upload + parse pipeline on Next.js with Prisma over SQLite for fast solo iteration.

  • Result

    Live product at spectre.asia. Built and shipped end-to-end as a solo project — used as a working example of productized AI tooling for small teams.

Problem

Operators and managers regularly receive raw spreadsheet exports (sales, ops, inventory, performance) that take hours to manually parse into something a leadership team can act on.

Constraints

  • Output briefs must remain accurate and avoid LLM hallucination on numerical data
  • Upload flow must handle messy real-world spreadsheets (mixed schemas, inconsistent headers, partial data)
  • Hosting and inference cost has to stay viable at low usage volume during early access

Delivery

  • Built the upload + parse pipeline on Next.js with Prisma over SQLite for fast solo iteration.
  • Designed the LLM prompting layer to ground briefs in the actual data, not free-form summarization.
  • Deployed end-to-end on a VPS with predictable cost and zero per-call infrastructure overhead beyond the LLM API.
  • Shipped early access at spectre.asia for direct user feedback before broader rollout.

Result

  • Live product running at spectre.asia, available for early access.
  • Validated the core upload-to-brief flow end-to-end with real spreadsheets.
  • Established the foundation for future productization (multi-tenant, billing, custom brief templates).

Tech stack

  • Next.js
  • Prisma
  • SQLite
  • OpenAI
  • VPS Deployment

Related delivery proof across internal tools, automation, Android + AI, and supporting product systems.

Client Systems

Client delivery

Enterprise CRM - Sales Pipeline & Performance System

Lead Full-Stack Engineer6-week delivery sprint

Cut the weekly pipeline review cycle from ~2 days of spreadsheet reconciliation to ~15 minutes — single source of truth across sales, ops, and management.

  • Problem

    Pipeline updates and performance reporting were split across 3 separate spreadsheets, making weekly reviews take days and ownership hard to trust.

  • My scope

    Mapped sales stages, reporting rules, and operator roles before touching schema or UI.

  • Result

    Cut the weekly pipeline review cycle from ~2 days of spreadsheet reconciliation to ~15 minutes — single source of truth across sales, ops, and management.

  • Laravel
  • Next.js
  • PostgreSQL
Read case study

Automation Systems

Client delivery

Inbound Order & Lead Ops Automation

Automation Engineer2-week delivery sprint

Eliminated an estimated 60–80 hours/month of manual data entry across multi-branch operations. Booking + reporting now flow automatically into a single source of truth.

  • Problem

    Inbound orders, bookings, and chat updates were copied manually into spreadsheets across multiple branches, producing inconsistent records, delayed follow-up, and zero operational visibility for management.

  • My scope

    Implemented web-order-to-sheet automation with validation and normalization.

  • Result

    Eliminated an estimated 60–80 hours/month of manual data entry across multi-branch operations. Booking + reporting now flow automatically into a single source of truth.

  • n8n
  • Google Apps Script
  • Google Sheets
Read case study

Platform Delivery

Client delivery

Multi-Surface Platform Monorepo

Monorepo Platform Engineer4-week delivery sprint

Reduced release friction and dependency drift across the platform.

  • Problem

    Separate repositories for related surfaces caused dependency drift and slowed coordinated releases.

  • My scope

    Structured the repository with npm workspaces and clearer package boundaries.

  • Result

    Reduced release friction and dependency drift across the platform.

  • npm workspaces
  • Next.js
  • NestJS
Read case study

Planning a similar build?

Share the workflow, delivery risk, and timeline. I will reply with the best starting scope.