Copy & bios

Paste these as written. Character counts are checked against each platform's limit.

Core lines first, then every bio field per platform, then the handle plan and the link-in-bio page. The pinned / welcome posts live on each platform page.

01 — Core lines
Belief line (leads everywhere)65 charsOpen with this on every profile, pinned post, and intro. It is the one line that explains the name.
People may call the outcome luck. We focus on the work behind it.
Formal descriptor (verbatim)71 charsUse exactly this wherever a platform asks for a one-line description or category text.
A practical community for learning, building, and creating opportunity.
Primary CTA (every channel)62 charsOne CTA per post. Do not stack it with newsletter, Discord, and follow asks in the same piece.
Reserve a seat at the next Build Night → workbehindtheluck.com
Short CTA (captions, video end cards)32 chars
Join the next Build Night ↓ link
Primary tagline (structure, not headline)39 charsUse as pillar names, highlight covers, section headers. Not as a standalone hook.
Learn. Practice. Build. Share. Connect.
Primary hashtag set109 charsSeven. Use two to four per post; always #WorkBehindTheLuck. Add #BuildNight on event posts and #Pampanga on local ones.
#WorkBehindTheLuck #DoTheWorkBehindIt #BuildForOpportunity #BuildNight #BuildInPublic #LearnByDoing #Pampanga
Supporting lines (banners, headers, section titles)
Header / banner line (preferred)64 charsBest for cover photos, banners, and page headers.
The work people don't see. The opportunities they eventually do.
Supporting line43 chars
Prepare for opportunity. Create more of it.
Supporting line39 chars
Build what others eventually call luck.
Supporting line65 chars
Real skills. Real projects. Real relationships. More opportunity.
Supporting line57 chars
Become ready. Make the work visible. Help others forward.
02 — Founder & community
Mat's one-line introduction238 chars
I'm Mat. I lead a platform engineering team, build products on the side, and I interview a lot of engineers. Most people I turn down aren't short on talent — they're short on finished work they can show. That's what this community is for.
Founder bio, short296/300
Mat Mozer leads a platform engineering team, builds products on the side, and interviews a lot of engineers. Most people he turns down are not short on talent; they are short on finished work they can show. He founded The Work Behind the Luck (weekly Build Nights, Pampanga + online) to fix that.
Founder bio, long933 charsAbout 155 words. For speaker pages, press, and the About page.
Mat Mozer leads a platform engineering team, builds products on the side, and interviews a lot of engineers. Most people he turns down are not short on talent. They are short on finished work they can show. That gap is why he founded The Work Behind the Luck, a practical, project-led community based in Pampanga with online access, where the outcomes people call luck get traced back to learning, practice, projects, relationships, and follow-through.

The community runs weekly Build Nights: a short practical lesson, an hour of guided work on whatever you brought, demos, and a next step before you leave. Mat teaches from real work, including the mistakes. He has ADHD and a graveyard of unfinished side projects; the community is partly how he makes himself finish things. He writes about building with AI without handing over your judgment and about getting out of tutorial hell.

He is easiest to find at the next Build Night.
Standard community description (any About field)594 charsAbout 100 words. Paste into any About field that allows a paragraph.
The Work Behind the Luck is a practical community for learning, building, and creating opportunity. Weekly Build Nights in Pampanga, with online access, are where people learn one useful skill, work on a real project, portfolio piece, or business problem with help in the room, and leave with progress and a clear next step. Members are students, developers, career changers, creators, and business owners who use AI and other practical tools to improve themselves, build useful things, share the evidence, and help one another. People may call the outcome luck. We focus on the work behind it.
03 — Bios by platform

Facebook

@workbehindtheluckSetup, specs & assets →
Page Intro (shown under the name)88/101
Weekly Build Nights in Pampanga + online. Bring something to build, leave with progress.
Page short description204/255
Weekly Build Nights in Pampanga + online. Bring something you want to learn, build, or improve. Leave with progress and a next step. A practical community for learning, building, and creating opportunity.
Page About (long)898 charsAbout 150 words.
The Work Behind the Luck is a practical community for learning, building, and creating opportunity. Build Nights run weekly in Pampanga, with online access.

Every Build Night works the same way: a short practical lesson you can use the same night, an hour of guided work on whatever you brought (a project, a portfolio piece, a workflow, a business problem), a hot seat or demos, and a next step before you leave. You do not need a finished idea or advanced skills. You need one thing you want to improve and the willingness to work on it in the room.

Members are IT students, developers, career changers, creators, founders, and local business owners who use AI and other practical tools to get better, build useful things, share the evidence, and help each other.

People may call the outcome luck. We focus on the work behind it.

Reserve a seat at the next Build Night → workbehindtheluck.com
Group description1092 charsAbout 170 words. Member questions for the join screen: (1) What are you learning or building? (2) What can you help someone else with? (3) Will you come to a Build Night in Pampanga or join online?
This is the community room for The Work Behind the Luck, a practical community for learning, building, and creating opportunity. Build Nights run weekly in Pampanga, with online access. People may call the outcome luck. We focus on the work behind it.

What happens here: introductions ("I am learning ___ / I can help with ___"), event threads, progress updates, project showcases, asks and offers, real business problems, recaps, and accountability. Beginners are welcome. Everyone participates.

Post this: what you are building or learning, a screenshot of real progress, a question you are stuck on, feedback for someone else, a job, internship, or real problem you can share, a lesson from something that went wrong.

Do not post this: spam, affiliate links, crypto, betting, get-rich-quick or make-money-fast offers, AI-news reposts with no work attached, or anything about another member without their consent.

When you join, answer the three questions and then introduce yourself in the pinned Start Here thread. Then reserve a seat at the next Build Night at workbehindtheluck.com.
Group rules1019 charsSeven rules. Paste each numbered line as a separate Facebook Group rule (title = first sentence, detail = the rest).
1. Show the work. Posts should be about something you are learning, building, stuck on, or able to help with. Screenshots, drafts, and rough versions are welcome.
2. Help freely, review honestly. Give feedback that makes the work better. Be specific and be kind. No put-downs, no piling on.
3. Beginners belong here. Do not gatekeep. Do not answer a question with "just Google it."
4. No spam, no selling, no schemes. No affiliate links, crypto, betting, get-rich-quick, make-money-fast, or MLM. Opportunity posts (jobs, internships, real problems, collaborations) are welcome when they are specific.
5. Consent before you post about someone else. No photos, quotes, screenshots of chats, or project details from another member without their clear yes.
6. Own your judgment. Share AI-assisted work, but say so when it matters, and stay responsible for its quality and consequences.
7. Keep it useful. One idea per post. Ask before posting the same thing across many threads. Moderators may remove posts that do not fit.

Instagram

@workbehindtheluckSetup, specs & assets →
Name24/30
The Work Behind the Luck
Bio147/150
Weekly Build Nights in Pampanga + online. Bring something to build, leave with progress.
Learn. Practice. Build. Share. Connect.
Next Build Night ↓
Website29 chars
https://workbehindtheluck.com

TikTok

@workbehindtheluckSetup, specs & assets →
Name24/30
The Work Behind the Luck
Bio73/80
Build Nights in Pampanga + online. Bring a project, leave with progress ↓
Website29 chars
https://workbehindtheluck.com
Display name24/50
The Work Behind the Luck
Bio154/160
Weekly Build Nights in Pampanga + online. Bring something to build, leave with progress. People may call the outcome luck. We focus on the work behind it.
Location21/30
Pampanga, Philippines
Website29/100
https://workbehindtheluck.com

DEV.to

@workbehindtheluckSetup, specs & assets →
Profile bio179/200179/200. This is Mat's personal DEV.to profile.
I lead a platform engineering team and interview a lot of engineers. Founder of The Work Behind the Luck: weekly Build Nights in Pampanga + online. I write about finishing things.
Organization summary213/250
A practical community for learning, building, and creating opportunity. Weekly Build Nights in Pampanga + online: one useful lesson, an hour of guided work on your project, demos, and a next step before you leave.
Organization About743 charsAbout 115 words.
The Work Behind the Luck is a practical community for learning, building, and creating opportunity. Build Nights run weekly in Pampanga, with online access; developers, students, career changers, and builders learn one useful skill, work on something real, and leave with a next step.

This organization publishes what comes out of the room: lessons from Build Nights, build-in-public updates on the community site (Next.js, Tailwind, Prisma, tRPC), member project writeups, and honest posts about building with AI without handing over your judgment. Expect tradeoffs, iterations, and what went wrong, not hype.

People may call the outcome luck. We focus on the work behind it. Reserve a seat at the next Build Night at workbehindtheluck.com.
Brand color7 charsAmber. Enter in the organization settings color field.
#f2a33c
Organization tag line59/60
The work people don't see. The opportunities they later do.
Organization name24/5024/50. Username: workbehindtheluck (17, within 2 to 30).
The Work Behind the Luck
Organization proof (required: your association with the org)380/1500
I'm Mat Mozer, founder of The Work Behind the Luck, a practical community with weekly Build Nights in Pampanga, Philippines, plus online access. I own and operate workbehindtheluck.com (see workbehindtheluck.com/about, which names me as founder) and my DEV.to account email is on that domain. I run the events, write the community's articles, and will be the organization's admin.
Organization CTA button text18/20
Join a Build Night
Organization CTA body (markdown)208/256
Weekly Build Nights in Pampanga + online. One practical lesson, an hour of guided work on your project, a next step before you leave. Beginners welcome. [Reserve a seat](https://workbehindtheluck.com/events).
Canonical URL rule242 chars
DEV.to is the original for the community's articles, so leave canonical_url empty in the front matter. Only set canonical_url (pointing at the workbehindtheluck.com/blog URL) when cross-posting an article that was published on the site first.
04 — Handles
Handle plan721 chars
Primary handle is workbehindtheluck on Instagram, TikTok, the Facebook Page, the Facebook Group web address (facebook.com/groups/workbehindtheluck), and the DEV.to organization. X caps handles at 15 characters, so X is workbehindluck. If a primary is taken, fall back to thewbtl, then workbehindluck (wbtl is already taken on X and TikTok, so it is off the list). Instagram and Facebook only confirm availability inside the logged-in sign-up form, so check there. TikTok allows a username change once every 30 days, so get it right the first time. If sign-up allows, also reserve workbehindluck on Instagram and TikTok as a cheap defensive alias. The website is workbehindtheluck.com and it is the only link in every bio.
PlatformHandleBackupsLimit
Facebook@workbehindtheluckthewbtl · workbehindluck50
Instagram@workbehindtheluckthewbtl · workbehindluck30
TikTok@workbehindtheluckthewbtl · workbehindluck24
X@workbehindluckthewbtl15
DEV.to@workbehindtheluckthewbtl · workbehindluck30
05 — Link in bio
Link-in-bio headline46 chars
Bring something to build. Leave with progress.

The link-in-bio page is on this site at workbehindtheluck.com/links — no third-party tool, so it never goes stale and tracks with Vercel Analytics. Use that URL in every bio.

  • Reserve a seat at the next Build Night/events
  • New here? Start here/start-here
  • Join the community/join
  • Discord#discord · set NEXT_PUBLIC_DISCORD_INVITE_URL
  • Lessons and recaps/blog
  • Mentor, teach, or bring a business problem/get-involved
  • Contact/contact
06 — Writing under the brand
  1. 01Lead with the belief line or a concrete fact, never with the brand name. People may call the outcome luck. We focus on the work behind it.
  2. 02One idea per post. One call to action per post. The CTA is the next Build Night unless there is a specific reason it is not.
  3. 03Show the work: the problem, the thinking, the tradeoffs, the iterations, and the result. If a post has a result with no process, it is not ours.
  4. 04Be concrete in the first eight words. Name the place (Pampanga), the format (Build Night), or the thing that happened. Concreteness is how we disambiguate from gambling, get-rich-quick, and hype. Denials are not.
  5. 05Consent before anyone else appears. No photo, quote, name, or project detail from a member without their explicit yes to that specific use. Note the consent in the post.
  6. 06Never use: manifest, secret system, guaranteed, passive income, unlock abundance, financial freedom, overnight, this one trick, doors will open. Prefer: practical, hands-on, project-based, useful, measurable progress, mentorship, accountability, judgment, consistency, real work.
  7. 07Personal channels sound like Mat (here is what I learned or built). Community channels sound like the room (here is what members are doing and how to join). A light '— Mat' byline is fine on community posts at launch.
  8. 08Short sentences. Plain words. No emoji in bios except one arrow for the link; sparing emoji in casual posts. Recaps report behavior, not vanity: people, first-timers, commitments, projects moved forward.
  9. 09Write as 'I' until there are members in the room; switch to 'we' when it is true. The belief line is the exception: its 'we' is Mat plus the reader.
  10. 10One plain line of dry humour per post is allowed; sermons are not.
  11. 11End every post in a verb someone can do this week.