Petfendy

Petfendy — All-in-one pet services, built with Kilo Code.

Comment

Inspiration

Pet owners typically have to juggle separate channels for care (hotel/daycare) and safe transport (pet taxi): WhatsApp messages, calls, unclear availability, and “price later” uncertainty.
I wanted to build a single, pet-first workflow that makes the process fast, transparent, and trustworthy—so owners can book confidently and pets experience less stress.

What it does

Petfendy is a pet-friendly platform that enables:

  • Pet profiles (age, breed, vaccination status, special notes)
  • Pet hotel & daycare bookings (Ankara-focused operations)
  • Pet taxi bookings (Ankara + intercity / nationwide coverage)
  • Clear pricing logic and structured booking flow (request → validation → confirmation → payment-ready)

How we built it

I built Petfendy end-to-end using Kilo Code to accelerate implementation while keeping the product modular and maintainable.

High-level architecture: [ \text{Web UI} \rightarrow \text{API} \rightarrow \text{Database} \rightarrow \text{Payment/Notifications} ]

Key modules:

  • Booking Engine: availability checks, date-range rules, overlap prevention
  • Pricing Engine: service-based pricing + distance-based pricing + add-ons
  • Domain Model: Pets, Owners, Services, Bookings, Pricing rules

Example pricing model (pet taxi): [ \text{Total} = B + (d \cdot r) + \sum_{i=1}^{n} A_i ] Where (B)=base fee, (d)=distance (km), (r)=per-km rate, (A_i)=add-ons (carrier, time window, etc.)

Challenges we ran into

1) Booking overlaps & availability
The tricky part was preventing invalid reservations and enforcing service rules. For overlap detection: [ \text{overlap} \iff \neg (e_1 \le s_2 \ \lor\ e_2 \le s_1) ]

2) Trust & safety constraints
Pet services are trust-heavy. I needed pet data (vaccination status/notes) to remain tightly coupled to bookings and visible at decision points.

3) Nationwide pet taxi edge cases
Intercity coverage introduces pricing and operational complexity. I designed the pricing system to be configurable (zones/rates/add-ons) to evolve without refactoring core logic.

Accomplishments that we're proud of

  • Delivered a complete end-to-end flow: pet profile → service selection → booking → validation → pricing → payment-ready
  • Implemented a modular Booking + Pricing core that can scale with new services and rules
  • Built a real usable product (not just a prototype screen) under hackathon constraints with Kilo Code

What we learned

  • AI-assisted building is strongest with a tight loop: spec → generate → test → refine
  • The real complexity lives in domain rules (availability, cancellation, safety policies), not UI
  • Keeping the core modular early (Booking/Pricing) saves time later and makes iteration faster

What's next for Petfendy

  • Notifications: confirmations, reminders, status updates
  • Admin/ops panel: capacity planning, schedules, taxi dispatch workflows
  • Trust layer: reviews, verified checklists, service standards
  • Logistics optimization for pet taxi routing: [ \min \sum \text{route_cost} \quad \text{s.t. time windows, pet constraints} ]
  • Expand partnerships and coverage while maintaining consistent safety and care quality

Built With

Share this project:

Updates