Treecard product work (freelance)

Context

I started working with Treecard in April 2023 as a freelance contractor in a request-driven model. The engagement is ongoing: they still bring me in for specific scopes when needed.

I worked directly with different stakeholders depending on the initiative, including a founder, designer, engineers, and non-technical collaborators.

What I built

1) Growth and conversion surfaces

• Implemented multiple production landing pages from Figma with direct feedback loops.
• Built mobile.treecard.org with the full acquisition flow: zip input, coverage check, plan options, and order details collection.
• Built recycle.treecard.org as a complete multi-step flow for device recycling/resale inputs and pricing.

2) Wildhero MVP

• Built the first versions of wildhero.com, including landing page and the initial web email client.
• Implemented the full frontend for inbox usage flows in that first version.
• Implemented a temporary Go backend to unblock end-to-end product testing, including caching and core app wiring.
• That backend was MVP-grade and not production-ready; the long-term backend was later handled by a dedicated team.

3) Additional initiatives

• Contributed to a Shopify Hydrogen ecommerce remake that reached near-complete scope before the initiative was canceled.
• Later contributed occasional updates to the Wildhero Chrome extension after the product direction pivoted from standalone client usage.

Delivery model

This was not a strict sprint process. Work came in intense windows with high delivery speed, often shipping rapidly until a milestone was hit or scope changed.

Outcomes

• Shipped multiple user-facing surfaces used for acquisition and product validation.
• Delivered early Wildhero product versions quickly enough to support team scaling and handoff.
• Maintained long-term trust with the company through repeated re-engagements over multiple years.
• Earned referral-based trust: a hiring manager I worked with later referred me into another company.

What I learned

• High-speed execution needs sustainable pacing. I learned to calibrate effort and avoid unsustainable bursts.
• It is important to raise scope risk early and clearly state when a project grows beyond what one engineer can own alone.
• For MVP phases, separating prototype backend work from production backend ownership helps teams move fast without confusion.