Schilazzi P. Towe
Start a conversation

Frontier

Full-stack development for products that last

I build web applications end to end, from the data model to the interface people use, so a first version can become a product without starting again. You own everything, and it comes with tests and documentation that another developer can pick up.

What I build

  • First versions of products (MVPs) that are small in scope but solid underneath.
  • Portals and workflow systems that replace paperwork, spreadsheets and email chains.
  • Rebuilds of slow or fragile systems, in stages, without stopping the business.
  • Integrations between payment, messaging, data and AI services.
  • Interactive and 3D web experiences that stay fast and readable by search engines.

How I approach it

  • Boring technology where it counts. Proven tools for data and money; new tools only where they clearly help.
  • Small releases. You see working software early and often.
  • Performance and accessibility from the start, not as a final polish.
  • Security by default: least privilege, validated input, secrets out of code, and sensible headers.

Typical stack

TypeScript, React and Next.js; NestJS and Python services; PostgreSQL and Supabase; three.js, GSAP and WebGL for interactive work; deployed to Vercel, Cloudflare or your own infrastructure.

Proof

  • e-Serbisyo: a connected town-hall system for 20 offices (working prototype).
  • PasinPay: a mobile-wallet prototype on a double-entry ledger with database-level safeguards.
  • ClassPulse: grading, evaluations and parent reports for a school program (in development).
  • A national aviation regulator's portal: an independent concept rebuild with a 424-document reader.
  • Process engine: a plain three.js and WebGL piece you can explore in the Lab.

Frequently asked

Freelancer or agency? An agency gives you a team and process; one builder gives you speed and a single point of responsibility. For focused products, one accountable builder is usually faster. For large teams and round-the-clock support, an agency fits better.

Who owns the code and hosting? You do: your repository, your hosting accounts, your domain.

What happens after launch? Agreed up front: a documented handover, a support window, or ongoing development.

Start a conversation