Contact person: Business Client

Phone:Show

Email:Show

Location: Cebu City, Philippines

Budget: Recommended by industry experts

Time to start: As soon as possible

Project description:
"Phase 1 starts with a deep dive into our current stack. The most urgent pain point is Twilio: messages simply never reach some users or reach them far too late, and the pattern seems tied to certain carriers. I need you to trace the root cause, implement a reliable fix, and document what changed.

While you are inside the codebase, upgrade Node.js to the latest stable LTS, profile the app for slow-loading pages, and squash the intermittent login failures that keep appearing in our logs. I’m looking for clear, reproducible steps that prove each issue is resolved and a short write-up that flags any other weaknesses you spot.

Phase 2 shifts to strategy. Our content team struggles with Prismic slices; routine edits turn into dev tickets. I want an informed recommendation on whether we stay, migrate to Webflow, or consider another CMS entirely—backed by a comparison of maintenance overhead, editor experience, and extensibility. At the same time, outline alternatives to Twilio for real-time trade notifications, including the option of building a lightweight in-house app.

Deliverables
• Fixed and verified Twilio SMS flow (no missing or delayed messages on affected carriers)
• Node.js upgraded and regression-tested
• Performance and login issues resolved, with before/after benchmarks
• Technical report summarising findings, additional risks, and optimisation suggestions
• CMS comparison memo and notification strategy proposal

Code lives in a private GitHub repo; I’ll provide access on acceptance. Please mention relevant Node.js, Twilio, or CMS migrations you’ve handled so I can gauge fit.

Website: [login to view URL]" (client-provided description)