Persona
CardCard for freelance developers.
A freelance developer's card has to do two jobs in one tap. It has to show the work — a portfolio, a GitHub, a recent stack — and it has to set the conversation, with a rate and a booking link the prospective client can act on without writing an email first. CardCard renders both, signed and Wallet-installable, from the same record. The card lives on the recipient's phone after a meetup, not in their inbox.
Why a Freelance developer picks CardCard
- GitHub username on the public face — recruiters and CTOs scan past the card straight into the actual work the developer ships.
- Hourly rate sits where it belongs — public, dated, no follow-up email needed for the question every prospect asks first.
- Booking calendar is one tap, both from the public page and from the Wallet pass — no calendar back-and-forth and no scheduling email volley.
An example Freelance developer card
Rauni Salo · Freelance developer · Independent
- GitHub: https://github.com/raunisalo (public)
- Rate: €95/hr · Helsinki time (public)
- Calendar: https://cal.com/rauni (public)
- Email: rauni@salo.dev (Wallet only)
Questions
- Can I show different rates for different work?
- Use the rate field for the headline number and link to a longer rate sheet from the GitHub or portfolio field. The card is the introduction, not the contract — keep the rate visible and the rate sheet a tap away.
- Should my email be public or Wallet-only?
- Public if you want inbound from anyone who scans the page. Wallet-only if you only want clients who actually held a card to reach you. Most freelancers we know pick Wallet-only and lean on the calendar link for cold inbound.
- Does the GitHub field work as a clickable link?
- If you set the field kind to URL, yes — the public page renders it as a clickable link and the Wallet pass surfaces it on the back of the pass for one-tap travel.
Reviewed by the CardCard atelier.