TipLedger Receipts
A widget that turns a creator's one-off supporter tips into a branded, downloadable receipt and thank-you page the supporter can keep and share.
One product, one founder, thirty days. Everything below is built to be executed inside the contest window — the official rules still decide what counts.
Decide in 20 seconds
The facts that decide whether this is worth thirty days of yours.
Independent creators already collecting tips, especially writers, podcasters, and streamers with 500-20,000 followers who link a tip page in bio.
Market demand 2.5/10
Narrow the buyer to a segment with an urgent, already-budgeted problem and reference the specific trigger event that creates willingness to pay.
Why this could work in 30 days: one founder can ship the MVP in 4 days; the plan targets a first sale on day 10; 53 sales at $19 clears $1,000 of collected revenue; strongest signal is speed to first revenue at 8.6/10.
Score and projections come from the generated report and are not guarantees. The $100K Hackathon is run by Ship or Die — read the official rules before you build.
Your first 24 hours
5 concrete actions. Tick them off as you go — nothing is saved or sent.
Product opportunity and positioning
Target customer
Independent creators already collecting tips, especially writers, podcasters, and streamers with 500-20,000 followers who link a tip page in bio.
Why now
Stripe Payment Links and link-in-bio tip pages are already standard, so the buyer has an audience and checkout before TipLedger is installed.
Problem
Supporters tip once and forget; creators lack a lightweight artifact that makes a tip feel worth repeating or sharing.
Solution
Creator pastes a tip link and brand details; each supporter fills a short form and gets an auto-generated receipt page with thank-you, amount, and share card.
TipLedger Receipts is a narrow add-on for creators who already collect tips. JEV scored the concept 56.1/100 (band C) with strong marks for speed to first revenue (8.57) and solo build feasibility (7.83), but weak market demand (2.51) and monetization (3.53). The plan does not pretend those weaknesses away. It compensates by picking a buyer with an existing tip flow, a visible link in bio, and an immediate reason to test a small artifact.
The buyer is a writer, podcaster, or streamer with 500-20,000 followers who already links a tip page. They do not need another payment processor. They need a reason for a supporter to feel something after the tip. Today the supporter pays and gets a generic confirmation. The creator gets money and no shareable proof. TipLedger turns that moment into a branded receipt page with a personalized thank-you, the amount, and a share card. The supporter can keep it, post it, or email it. The creator gets a lightweight retention and sharing loop without manual work.
Positioning is deliberately small: not a tipping platform, not a membership tool, not a payout product. It sits on top of an existing Stripe Payment Link or tip page. The creator pastes the link and brand details. The supporter opens a TipLedger page, enters name, amount, and message, sees the receipt, then clicks through to tip. After payment they return to the receipt and download the card. That is the whole product.
Why now: link-in-bio tip pages and Stripe Payment Links are normal. Creators already have an audience and a checkout. No marketplace cold-start, no new payment rail, and no procurement. The first customer is reachable by DM because the tip link is public.
The risk is that creators see this as cosmetic. The first 30 days test that directly: personalized sample receipts, free activations, and a paid $19 lifetime offer. If creators do not activate or share, the concept fails fast. If they do, the receipt becomes a small but repeatable add-on to a workflow they already run.
Smallest sellable MVP
A creator-branded receipt page and downloadable share card that sits behind an existing tip link, sold as a $19 lifetime add-on.
Must-have features
- Creator onboarding for brand name, slug, colors, thank-you text, and Stripe Payment Link
- Public tip page with amount presets, custom amount, supporter name, message, and optional email
- Signed receipt page at a public URL
- Server-rendered PNG share card via Satori
- Email delivery of the receipt link via Resend
- Creator dashboard listing receipts
- CSV export of receipts
- Settings editor for brand details
Explicitly out of scope
- Memberships or subscription billing
- Marketplace or creator discovery feed
- Payout handling or Stripe Connect
- Mobile app
- Tax invoices or accounting exports
- Payment verification or chargeback handling
- Self-serve custom domains (manual Vercel alias for Pro buyers at launch)
- Multi-language support
Demo flow (what the buyer sees)
- Open a sample creator tip page
- Enter supporter name, $5 amount, and a short message
- Show the branded receipt preview
- Click the creator's Stripe Payment Link
- Return to the receipt page
- Download the PNG share card
- Show the creator dashboard row
Technical implementation plan
Stack
Architecture
Supabase stores creators and receipts. The public page at /c/[slug] loads creator branding and renders the supporter form. A server action validates input and creates a receipt with a signed ID. The receipt page at /r/[id] renders the branded thank-you. The image route at /api/og/[id] renders and caches the share card. Resend sends the receipt link when an email is supplied. Stripe Payment Links are pasted, not called through an API, so TipLedger never touches payouts or card data.
Build steps
- Create Next.js TypeScript repo and Vercel project
- Create Supabase project with creators and receipts tables
- Add Supabase auth and protected dashboard route
- Build creator onboarding form
- Build public tip form at /c/[slug]
- Create signed receipt records from server action
- Build receipt page at /r/[id]
- Add /api/og/[id] Satori share-card route with fallback
- Send receipt email via Resend
- Build dashboard list and CSV export
- Deploy production and seed demo receipts
- Run mobile QA and fix layout issues
AI components
- None in MVP. The thank-you text is creator-authored and deterministic; no LLM is called.
Pricing and monetization
Lifetime
Entry offerFor Solo creators testing the add-on
- Unlimited receipt pages
- Share cards
- Email capture
Pro
For Creators with steady tip volume
- Custom domain
- Branded share cards
- CSV export
Model: One-time lifetime license per creator, with a $19 entry tier and a $49 Pro upgrade.
First revenue offer: I made a sample receipt for your tip page. Want it live free for 7 days? If it helps, $19 lifetime after.
Expected ACV: $22
Upsell path: After 20 receipts or a CSV request, offer Pro for custom domain, branded cards, and CSV export. Custom domain is fulfilled manually at launch.
First-customer acquisition
Direct DMs to creators who already list a tip link in bio on X and Instagram.
Where to find them
- X bios containing buymeacoffee.com, ko-fi.com, tip jar, or support me
- Instagram link-in-bio pages with a tip link
- Newsletter writers with a support or tip footer
- Podcast show notes with a support link
- Twitch streamers with a donation panel
- Indie hackers and developers with a buy-me-a-coffee link
- Substack writers with a tip jar page
Exact outreach motions
- Build a 50-row sheet of creators with visible tip links and recent posts
- Create a personalized mock receipt for the first 10 with their brand name
- DM 20 per day with one-line offer and sample link
- Follow up once after 3 days with the $19 lifetime checkout link
- Ask for one intro to another creator after a positive reply, with no incentive
Message template
Hey [Name] - I made a sample TipLedger receipt for [brand]: [link]. It gives every supporter a branded receipt and share card after they tip. Want it live on your tip page free for 7 days? If it helps, $19 lifetime after.
30-day execution roadmap
Week 1 · Build & validate · 5 days
Repo, database, deploy skeleton
- Create Next.js TypeScript repo and Vercel project.
- Create Supabase project with creators and receipts tables.
- Add environment variables and deploy skeleton.
Deliverable: Deployed skeleton with database schema.
Creator account and brand setup
- Add Supabase auth and protected dashboard route.
- Build onboarding form for brand name, slug, colors, thank-you text, and tip link.
- Validate slug uniqueness and save creator record.
Deliverable: Creator can sign up and save brand settings.
Public tip form and receipt creation
- Build /c/[slug] page with amount presets and custom amount.
- Add supporter name, message, and optional email fields.
- Create server action to write receipt with signed ID.
Deliverable: Supporter form creates receipt record.
Receipt page, share card, email
- Build /r/[id] branded receipt page.
- Add /api/og/[id] Satori image route with fallback.
- Send receipt email via Resend when email is provided.
Deliverable: End-to-end receipt page, PNG card, and email.
Dashboard, deploy, mobile QA
- Build dashboard list with copy-link and CSV export.
- Test full flow on mobile and fix layout issues.
- Deploy production and run 3 demo receipts.
Deliverable: Live MVP at public domain with demo receipts.
Week 2 · Launch & first sale · 5 days
Personalized proof assets
- Create 10 sample receipts for target creators.
- Capture screenshots and short demo links.
- Record 60-second Loom-style walkthrough.
Deliverable: 10 personalized samples plus demo video.
List, scripts, checkout
- Build 50-creator list with visible tip links.
- Write DM script and follow-up.
- Create Stripe Payment Link for $19 Lifetime.
Deliverable: 50-row list, scripts, live checkout.
First DM batch
- Send 20 DMs with personalized sample links.
- Log replies in a simple sheet.
- Fix any onboarding blocker reported.
Deliverable: 20 DMs sent and tracked.
Second batch and follow-up
- Send 20 more DMs.
- Follow up day-6 batch once.
- Add FAQ from replies to onboarding.
Deliverable: 40 total DMs and updated FAQ.
Close first paid creator
- Send 10 DMs to warmest segment.
- Offer free 7-day activation with $19 lifetime after.
- Ask for payment link click and assist setup.
Deliverable: First paid sale or 3 active trials.
Week 3 · Repeat & systematize · 7 days
Onboard trials manually
- Set up receipt pages for each trial creator.
- Collect friction notes in a shared doc.
- Ask each trial to share one supporter receipt.
Deliverable: 3 active creators with live receipt pages.
Ship top two fixes
- Fix mobile preview and thank-you copy issues.
- Add receipt page share buttons.
- Deploy and notify trial users.
Deliverable: Updated deploy with two fixes.
Convert non-repliers
- Follow up all non-repliers with $19 link.
- Post demo in 2 indie creator communities.
- Track click and reply rates.
Deliverable: 10 follow-ups and 2 community posts.
Funnel metrics and segment choice
- Calculate DM reply, activation, and paid rates.
- Pick best segment: writers, podcasters, or streamers.
- Write next-week outreach target list.
Deliverable: Segment decision and 40 new targets.
Add $49 upgrade
- Create Pro checkout link and upgrade page.
- Gate CSV export and custom domain request.
- Write manual custom-domain runbook.
Deliverable: Pro tier purchasable.
Podcaster and newsletter samples
- Create 10 samples for podcasters and newsletter writers.
- Use their show or newsletter name in the card.
- Add samples to outreach sheet.
Deliverable: 10 new personalized samples.
Podcasters and newsletters
- Send 25 DMs to podcasters and newsletter writers.
- Use sample link in first message.
- Log replies and objections.
Deliverable: 25 DMs sent.
Week 4 · Scale what works · 11 days
Share card templates
- Add 3 share-card templates: minimal, bold, receipt.
- Let creator pick template in settings.
- Test rendering on mobile and desktop.
Deliverable: Template picker live.
Post-tip sharing
- Add share prompt and copy-link button on receipt page.
- Add Open Graph tags for receipt pages.
- Track share button clicks.
Deliverable: Receipt sharing loop shipped.
Streamers and Twitch
- Send 25 DMs to streamers with donation panels.
- Offer a stream-overlay-friendly receipt card.
- Follow up day-17 batch once.
Deliverable: 25 DMs sent and 10 follow-ups.
Public launch post
- Publish demo post on X and Indie Hackers.
- Include one sample receipt and clear $19 offer.
- Reply to every comment within 2 hours.
Deliverable: Public launch post live.
Collect real quotes
- Ask active users for a one-line quote.
- Request permission to use brand name and quote.
- Add approved quotes to landing page.
Deliverable: Up to 2 approved quotes or no-op.
Simple referral loop
- Add referral code field to checkout.
- Give free Pro upgrade for 3 paid referrals.
- Email active users about referral.
Deliverable: Referral page and tracking.
Newsletter writers
- Send 30 DMs to newsletter writers with tip jars.
- Use subject-line sample receipt.
- Log best-performing message.
Deliverable: 30 DMs sent.
Checkout and FAQ
- Rewrite checkout page with 3 objections handled.
- Add FAQ: what it is, Stripe link, refunds.
- Test checkout on mobile.
Deliverable: Higher-clarity checkout page.
Paid test prep
- Draft one sponsored-post test with $30 cap.
- Define stop rule: fewer than 10 clicks.
- Do not launch until DM reply rate is known.
Deliverable: Ad test ready with stop rule.
Trial conversion
- Follow up all trials with $19 deadline.
- Offer help setting tip link.
- Log conversion reasons.
Deliverable: 20 follow-ups sent.
CSV and custom domain
- Ship CSV export for Pro buyers.
- Run manual custom-domain setup for any Pro buyer.
- Document delivery checklist.
Deliverable: Pro deliverables fulfilled.
Days 29-30 · Consolidate · 2 days
Final metrics and fixes
- Update funnel sheet with sales, refunds, fees.
- Fix top support issue.
- Prepare final push list of 25 warm leads.
Deliverable: Metrics sheet and final push list.
Close and reconcile
- Send 25 final DMs and post launch update.
- Reconcile Stripe payments and refunds.
- Record final customer count and lessons.
Deliverable: Final sales count and reconciled ledger.
Revenue and profit scenarios
How the numbers are defined
Hackathon profit — Collected revenue − refunds − chargebacks − payment processing fees − paid marketing spend.
Business profit — Hackathon profit − operating costs (hosting, domains, tooling, AI/API delivery costs).
The contest ranks entrants on hackathon profit only. Hosting, tooling and AI/API delivery costs are not deducted by the organisers, but each sale still has to cover them — so we show both. Definitions verified on 2026-11-15 against the official rules.
Stated assumptions
- Conservative: 12 buyers from about 250 DMs and 3 free activations.
- Base: 40 buyers from 500 DMs, 2 community posts, and trial follow-up.
- Upside: 80 buyers with a 15% Pro mix and one small sponsored-post test.
- Stripe fees assumed at roughly 5% blended because small tickets carry the $0.30 component.
- Refunds modeled at 0% conservative, about 2% base, and about 2% upside.
- No chargebacks modeled in any scenario.
- No paid ads in conservative and base; upside includes $120 sponsored-post spend.
- Operating costs cover Vercel, Supabase, Resend, domain, and image rendering.
- No existing customers, partnerships, or verified revenue are claimed.
Conservative
12 customers- Refunds
- $0
- Chargebacks
- $0
- Payment fees
- $13
- Paid marketing
- $0
- Hackathon profit
- $239
- Operating costs
- $25
- Business profit
- $214
Base case
40 customers- Refunds
- $19
- Chargebacks
- $0
- Payment fees
- $45
- Paid marketing
- $0
- Hackathon profit
- $836
- Operating costs
- $55
- Business profit
- $781
Optimistic
80 customers- Refunds
- $40
- Chargebacks
- $0
- Payment fees
- $96
- Paid marketing
- $120
- Hackathon profit
- $1,664
- Operating costs
- $110
- Business profit
- $1,554
Model your own numbers
Runs in your browser · nothing is saved- Collected revenue
- $760
- Payment fees (3.9%)
- $30
- Paid marketing
- $0
- Hackathon profit
- $730
- Business profit
- $675
Hypothetical arithmetic, not a forecast. The fee rate is a flat 3.9% assumption, refunds and chargebacks are left at zero here, and none of this is tracked data.
Scenario models from stated assumptions, not verified revenue. No customers, revenue, partnerships, or sources are claimed.
Main risks and validation experiments
Risk 1Low DM response rate.
Use personalized sample receipts and narrow the segment to creators with visible tip links and recent activity.
Send 20 DMs and measure replies within 72 hours.
Change segment if fewer than 2 replies after 100 DMs.
Risk 2Creators see the receipt as cosmetic.
Show the share card and email capture, not just the receipt page, and track sharing behavior.
Ask 3 trial creators whether any supporter shared a receipt.
Drop the sharing angle if fewer than 10% of receipts are shared after 50 receipts.
Risk 3Stripe link setup friction blocks activation.
Accept any URL and provide one-screen instructions plus manual setup help for early users.
Watch 5 creators onboard without assistance.
Rework self-serve onboarding if fewer than 50% complete without help.
Risk 4Copycats or creator indifference.
Win with speed, niche templates, and direct relationships; do not spend on defensibility before a paid cohort.
Compare DM reply rate against a generic tip-tool message.
Narrow to podcasters or newsletter writers if no paid cohort by day 20.
Hour-by-hour: the first 24 hours
Hours 1-2
- Create Next.js repo, Vercel project, Supabase project, and domain.
Output: Deployed skeleton.
Hours 3-4
- Add schema, auth, and onboarding form.
Output: Creator can save brand settings.
Hours 5-6
- Build public tip form and receipt page.
Output: Working receipt URL.
Hours 7-8
- Add Satori share card and Resend email.
Output: PNG share card and email delivery.
Hours 9-10
- Deploy, create 3 demo receipts, and build a 20-creator list.
Output: Live demo and first outreach batch.
Full 30-day launch report
Read the full generated report
TipLedger Receipts - 30-Day Launch Report
1. Product opportunity and positioning
TipLedger Receipts is a narrow add-on for creators who already collect tips. JEV scored the concept 56.1/100 (band C). The score is honest: speed to first revenue and solo build feasibility are strong; market demand and monetization are weak. The plan compensates by narrowing the buyer to a creator with an existing tip link and an audience, then selling a small artifact that improves a moment they already own.
The buyer is a writer, podcaster, or streamer with 500-20,000 followers who links a tip page in bio. They do not need another payment processor or membership tool. They need a reason for a supporter to feel something after tipping. Today the supporter pays and gets a generic confirmation. The creator gets money and no shareable proof. TipLedger turns that moment into a branded receipt page with a thank-you, amount, and share card. The supporter can keep it, post it, or email it. The creator gets a sharing loop without manual work.
Positioning is deliberately small. It is not a tipping platform. It sits on top of an existing Stripe Payment Link or tip page. The creator pastes the link and brand details. The supporter enters name, amount, and message, sees the receipt, then clicks through to tip. After payment they return to the receipt and download the card. That is the whole product.
Why now: link-in-bio tip pages and Stripe Payment Links are normal. Creators already have an audience and a checkout. There is no marketplace cold-start, new payment rail, or procurement. The first customer is reachable by DM because the tip link is public.
The main risk is that creators see this as cosmetic. The 30 days test that with personalized sample receipts, free activations, and a $19 lifetime offer. If creators do not activate or share, the concept fails fast. If they do, the receipt becomes a repeatable add-on.
2. Smallest sellable MVP
The sellable unit is a creator-branded receipt page and share card behind an existing tip link. The creator saves brand name, slug, two colors, thank-you text, and Stripe Payment Link. TipLedger gives them a public tip page. A supporter enters name, amount, and message, sees a receipt preview, clicks the creator's tip link, and returns to a receipt page with a downloadable PNG card. If email is supplied, Resend sends the receipt link.
Must ship: onboarding, public tip form, receipt page, server-rendered share card, email capture, dashboard list, CSV export, and settings editor. Do not ship memberships, subscriptions, marketplace discovery, payouts, mobile app, tax invoices, payment verification, or self-serve custom domains. Custom domain is a manual Vercel alias for Pro buyers at launch.
Demo flow: open a sample creator page, enter a name and $5, show the branded receipt, download the card, then show the dashboard row. This is enough to sell $19 because the buyer already has the tip link and audience.
3. Technical implementation plan
Stack: Next.js App Router on Vercel, TypeScript, Tailwind, Supabase Postgres and Auth, Stripe Payment Links, Resend, and Satori with resvg for PNG cards. No AI is needed; thank-you text is creator-authored.
Architecture: Supabase stores creators and receipts. /c/[slug] loads branding and renders the supporter form. A server action validates input and creates a receipt with a signed ID. /r/[id] renders the thank-you. /api/og/[id] renders and caches the share card. Resend sends the receipt link. Stripe Payment Links are pasted, not called through an API, so TipLedger never touches payouts or card data.
Build order: repo and schema; auth and onboarding; public form; receipt page; share image; email; dashboard and CSV; deploy; seed demos; mobile QA. Hardest risk: serverless image rendering timing out or producing inconsistent fonts. Mitigate with a static fallback card, cached PNGs, signed receipt IDs, and rate limits. Cap anonymous receipts per IP and per creator per hour to stop spam.
4. Pricing and monetization
Pricing is one-time: $19 Lifetime for unlimited receipt pages, share cards, and email capture; $49 Pro for custom domain, branded share cards, and CSV export. One-time is correct for a small add-on. It avoids subscription billing, dunning, and cancellation support in a 30-day sprint. Pro is for creators with steady tip volume and a reason to match their domain.
The first revenue offer is a free 7-day activation followed by a $19 lifetime link. Do not discount below $19. Expected blended first-year value is about $22 because most buyers take Lifetime and a minority upgrade to Pro. The upsell trigger is usage: after 20 receipts or a CSV request, offer Pro. Do not add a subscription in the 30 days.
5. First-customer acquisition
The primary channel is direct DMs to creators who already list a tip link in bio on X or Instagram. Build a 50-row list with name, platform, tip link, recent post, and segment. Create a personalized sample receipt for the first 10. Send 20 DMs per day, log replies, and follow up once after three days. Do not cold-email a purchased list. Do not run ads before 100 DMs.
Message: I made a sample receipt for your tip page, here is the link. It gives every supporter a branded receipt and share card after they tip. Want it live free for 7 days? If it helps, $19 lifetime after. Week-one goal: 50 DMs sent, 10 sample links opened, 3 free activations, 1 paid. If reply rate is below 2% after 100 DMs, change segment before changing the product.
6. Detailed 30-day execution roadmap
The JSON schedule is the operating calendar. Cadence: days 1-5 build and launch; days 6-10 create samples, send 50 DMs, target first paid sale by day 10; days 11-17 activate trials, ship fixes, add Pro, send 50 more DMs; days 18-24 add sharing loop, launch publicly, collect real quotes, send 55 more DMs; days 25-30 clarify checkout, follow up trials, fulfill Pro, reconcile.
Rules: one deploy per day unless a bug blocks activation. Every outreach day ends with a logged count. Every product day ends with a live change. The only paid contingency is a $30 sponsored-post test with a 10-click stop rule, only after 100 DMs. Do not build memberships, payouts, or a mobile app in the 30 days.
7. Revenue and profit scenarios
These are projections from stated assumptions, not verified revenue. Conservative: 12 buyers at $21 blended, $252 gross, no refunds or chargebacks, $13 fees, no ads, $25 operating cost. Base: 40 buyers at $22.50 blended, $900 gross, $19 refunds, $45 fees, no ads, $55 operating cost. Upside: 80 buyers at $24 blended, $1,920 gross, $40 refunds, $96 fees, $120 sponsored-post spend, $110 operating cost.
Stripe fees are modeled at roughly 5% blended because small tickets carry the $0.30 component. Hackathon profit subtracts refunds, chargebacks, payment fees, and paid marketing only. Business profit also subtracts hosting, domain, Supabase, Resend, and image rendering. No scenario claims existing customers, partnerships, or verified revenue.
8. Main risks and validation experiments
Low DM response. Mitigation: personalized samples and a narrow segment. Experiment: 20 DMs, measure replies in 72 hours. Kill or change segment if fewer than 2 replies after 100 DMs.
Creators see it as cosmetic. Mitigation: show the share card and email capture, not just the receipt page. Experiment: ask 3 trial creators whether any supporter shared a receipt. Kill the sharing angle if fewer than 10% of receipts are shared after 50 receipts.
Stripe link setup friction. Mitigation: accept any URL and give one-screen instructions. Experiment: watch 5 creators onboard. Kill self-serve if fewer than 50% complete without help.
Copycats. Mitigation: speed, niche templates, direct relationships. Experiment: compare DM reply rate against a generic tip-tool message. Do not spend on defensibility until there is a paid cohort. If no paid cohort by day 20, narrow to podcasters or newsletter writers.
9. First 24-hour action plan
Hours 1-2: create Next.js repo, Vercel project, Supabase project, domain. Output: deployed skeleton. Hours 3-4: add schema, auth, onboarding. Output: creator saves brand settings. Hours 5-6: build public tip form and receipt page. Output: receipt URL works. Hours 7-8: add Satori share card and Resend email. Output: PNG and email. Hours 9-10: deploy, create 3 demo receipts, build a 20-creator list. Output: live demo and first outreach batch.
This brief was generated from public data about established startups, then narrowed and scored for a solo 30-day launch. Revenue and profit figures are scenario models, not verified results, guarantees or evidence of existing customers. Validate demand yourself before you spend a month on it — and check the contest rules for what counts toward your score.
Related ideas
All ideas →Zéro Écart
A fixed-price catch-up service for French small businesses that are months behind on bookkeeping: upload a bank export plus a pile of receipts, and receive a finished, importable accounting journal, renamed receipts, and an itemised list of exactly what could not be matched.
CrateQuote Backline
CrateQuote Backline turns a small backline rental shop's gear inventory and a messy tour inquiry into a branded, availability-aware quote PDF and reply email in minutes.
ChaseLadder
A late-invoice escalation engine that runs a timed reminder ladder on any invoice a freelancer already sent, then generates a timestamped Chase Pack PDF for small-claims or collections handoff.