Creating the market for event financial software.
The founders understood finance and software. I understood the market. My job was to turn a technical payments product into a category the wedding industry could recognize, trust, and repeat back.
- Role
- Industry SME & strategic marketing contractor
- Context
- WedWallet is escrow-style payment infrastructure for weddings and events that cost as much as a house. Pre-launch, no category, no market language.
- Business question
- What category does this product belong to, and who has to believe in it first?
- What I owned
- Market narrative and category positioning
- Audience logic and message architecture
- Launch sequencing
- Executive positioning
- Partnership strategy
- Methods
- Industry expertise
- Competitive and category framing
- Audience segmentation by role
- Message testing with practitioners
- GTM planning
Scope and attribution. A three-month contract engagement. I was not a founder, officer, or full-time employee, and I did not build the product. Claims below describe strategy and marketing work I personally produced. Company performance beyond the public soft launch is not claimed because I do not have the data.
A modern wedding experience still ran on outdated payment operations.
Luxury weddings had been redesigned in nearly every dimension - planning, design, guest experience, documentation. The money had not. Couples, planners, and vendors were still moving six- and seven-figure sums through wire transfers, spreadsheets, bank portals, consumer payment apps, and scattered email confirmations.
Founder Andrea came from payments and fintech and saw the gap clearly as an infrastructure problem. What the company did not yet have was a way to describe the problem in language the wedding industry already used - or a view of which audience had to move first.
That is the gap I was hired into.
Weddings this expensive stop behaving like celebrations and start behaving like financial projects.
Once the event is framed as a project with contracts, milestones, approvals, and an audit trail, the product stops competing with payment apps and starts competing with the spreadsheet - a much easier argument to win, and a much better one for pricing.
I was the bridge between the product they built and the market they needed.
The mandate
Define the market narrative. Clarify the customer value. Build the launch system. Bring industry judgment into product and brand decisions.
- Industry expertise - planner relationships, vendor payment realities, and the etiquette around money in high-value celebrations
- Market strategy - audience definition, category positioning, message architecture, launch sequencing, partnership strategy
- Execution leadership - press materials, executive positioning, social and video strategy, publishing, cross-channel launch
- Product input - translating market expectations back into what the product and site needed to say and show
Four decisions had to be made before anything could be written.
A complex fintech product had to become understandable and desirable inside a relationship-driven luxury market. Each question below had a wrong answer that would have been expensive to discover after launch.
- 01
What category should WedWallet own?
Payment app, planning tool, bank-like service, or a new operating layer for wedding finance? The answer determined the competitive set, the pricing logic, and the objection we would spend the launch answering.
- 02
Who needs to believe first?
Couples control the money, planners influence adoption, vendors determine whether the workflow is practical. Sequencing these wrong stalls adoption at the first handoff.
- 03
How does a new brand earn financial trust?
The story had to explain custody, authorization, privacy, and records without losing the emotional relevance of the occasion, and without the generic security language that reads as evasive in fintech.
- 04
How should the market launch?
Press, founder visibility, social content, video, and partnerships each needed a distinct job inside one narrative, rather than four versions of the same announcement.
Reframing the competitive set.
What the evidence said
The market was not shopping for a better payment app. It was already coping - with spreadsheets, bank portals, consumer payment apps, and email threads used as the record of what had been agreed and paid.
The pain was not the transaction. It was reconstructing the state of the project: what is due, what was approved, what has been paid, and where the proof lives.
What I did about it
Positioned WedWallet as modern payments infrastructure for ultra-luxury events - purpose-built for a high-stakes event workflow, not a general-purpose wallet.
- Competitive set moved from payment apps to the spreadsheet-and-email status quo
- Value argument moved from convenience to control and record-keeping
- Language moved from fintech feature names to the industry's own vocabulary
One product. Three adoption problems.
The single most consequential call in the engagement. WedWallet does not have one customer - it has three parties with different relationships to the money, and a message that satisfies one can actively alarm another.
Control the funds
They need confidence that every contribution and payment is visible, authorized, and documented - including the family money that arrives with expectations attached.
Adoption risk: handing money to an unfamiliar brand.
Coordinate the workflow
They need operational visibility without holding client funds, and without chasing screenshots and confirmations to prove a vendor was paid.
Adoption risk: looking like a liability, not a tool.
Receive payment
They need a secure, low-friction process that fits existing business operations and does not slow down the deposit that lets them book the date.
Adoption risk: one more system they did not ask for.
Why this mattered
Planners are the distribution channel. They are consulted before the couple chooses tools and they carry the workflow across dozens of events a year, so a message that wins the planner compounds while a message that wins one couple does not.
What I did about it
Every piece of messaging had to answer three questions explicitly: who controls the money, who sees the workflow, and who receives payment.
Launch sequencing led with planner credibility - a vendor verification badge and a founding planners program - rather than consumer acquisition.
Four pillars, one promise.
The narrative paired financial control with the emotional relief of removing payment friction from a major life event. Each pillar exists to answer a specific objection.
| Pillar | The claim | The objection it answers |
|---|---|---|
| Category | Payment infrastructure built for high-value events, not another general payment app. | "We already have a way to pay people." |
| Function | One operating record. Contracts, due dates, approvals, transfers, and receipts stay connected. | "Our spreadsheet works fine." |
| Trust | Control before money moves. Customers authorize each payment while funds stay separate through sponsor bank infrastructure. | "Who is actually holding my money?" |
| Experience | Less money talk. Couples and planners spend less energy reconstructing payment status across tools. | "This is one more thing to manage." |
Know what is due, approve what moves, and keep the complete record.
The dashboard is where the strategy became legible.
The product story focused on operational visibility rather than abstract fintech features. What the market needed to see was a shared ledger, vendor-level context, and a clear control model - so that is what the interface story led with.
Couples and planners work from the same payment record, which removes the screenshot economy between them.
Contracts, invoices, balances, approvals, and receipts stay attached to the vendor they belong to.
The client authorizes payment while the planner retains visibility - the distinction that makes planners safe to adopt it.
Financial credibility could not rely on generic claims.
So the messaging explained the mechanics instead of asserting safety.
| Fund separation | Customer funds remain separate through sponsor bank infrastructure. |
| Explicit approval | Payments move only after the customer authorizes them. |
| Complete records | Each payment leaves a timestamped, downloadable record. |
I built the market-facing launch system.
Press established authority. Owned channels explained the product. Founder visibility added credibility without replacing the brand story. Partnerships extended reach into the industry's existing trust networks.
| Workstream | What I produced | Job inside the narrative |
|---|---|---|
| Positioning | Category definition, audience logic, core promise, proof points, messaging architecture | Make the product legible |
| Press & launch | Press kit, launch release, pitch concepts, media strategy, rollout sequence | Borrow third-party authority |
| Executive positioning | Founder commentary, interview preparation, social narratives | Put a credible person behind the claims |
| Social & video | Channel strategy, calendar, copy, publishing system, edited launch content | Explain the product repeatedly, in context |
| Partnerships | Wedding-industry relationships and a mission-aligned nonprofit partner | Enter through existing trust |
Fig. 05 - Operating assets produced during the engagement, plus video editing, executive positioning, and partnership development
I brokered WedWallet's first philanthropic partnership.
VOW for Girls gave a new brand a mission-aligned way to connect weddings with a couple's first act of giving as a new family - and connected WedWallet to a nonprofit already respected inside the wedding industry.
What I owned
Identified the opportunity, brokered the relationship, shaped the shared narrative, and moved the partnership toward launch content.
A technical product entered the market with language the industry could use.
What happened
WedWallet announced its soft launch on November 12, 2025, using the trust and transparency narrative developed during the engagement.
The live site still carries the audience logic, operating-system framing, security explanation, and planner-led workflow I helped shape - the positioning outlasted the contract.
What I am not claiming
I do not have post-launch revenue, sign-up, activation, or retention data, so no performance outcome is asserted here.
The verifiable results are the launch itself, the market-facing system that produced it, and the positioning still in use.
Notes & sources
- Fig. 01 spend figures are attributed to wedding-industry analyst Think Splendid as presented in the original engagement materials.
- Engagement: three-month contract with Perlyn, October–December 2025, as Marketing & Partnerships Manager for WedWallet.
- Product screenshots are the client's own marketing site and interface, reproduced as supporting evidence of the positioning in market.