FluentStack Specialist - Community, Booking, and Payments

Overview We're launching the first version of GoalOasis, a mentorship community for gamers, on WordPress. Mentors coach members through paid one-on-one video sessions; the community is where they meet. This is a configuration job, not a development job. The entire build runs on the WPManageNinja (Fluent) plugin suite — FluentCommunity, FluentBooking Pro, Fluent Forms Pro, FluentCRM, FluentSMTP. We've already made the architecture decisions. We need someone who knows this specific stack deeply and can assemble it correctly, quickly, and in a way that a non-technical team can run afterward. You will not be writing a plugin. You may occasionally write a small snippet — a shortcode, a conditional redirect, a role check — and you should be comfortable doing that safely. If your instinct on every requirement is "I'll build a custom plugin for that," you're overqualified and we're not the right fit. What you'll build 1. The community (FluentCommunity) Spaces, feeds, member profiles, roles and permissions, onboarding flow. A browsable mentor directory members can filter by game and skill area. Preserve our existing 18+ age-confirmation gate (already implemented as a user meta flag on both social and email/password signup) — do not break it. 2. One-on-one coaching bookings (FluentBooking Pro) Each mentor set up as a host with "manage only own calendar/events/bookings" permission, own availability, own calendar sync. Front-end panel configured so mentors manage their own bookings without ever seeing wp-admin. Stripe payments live on paid events, with confirmations, reminders, reschedule and cancellation flows. A "My Sessions" page for members using the booking list shortcode. 3. The negotiation-to-contract flow (Fluent Forms Pro + FluentCRM) Mentors and members agree their own price. Our flow: Member submits a coaching request form (goal, game, budget range, availability). Mentor and member discuss terms inside the community. Both parties ratify final agreed terms in a terms-confirmation form — this is the record of the deal, not a live negotiation engine. Submission triggers a FluentCRM sequence and hands off to booking at the agreed price. We'll walk you through the exact price-realization mechanism at kickoff; it uses native FluentBooking features, no code. 4. Lifecycle automation (FluentCRM + FluentSMTP) Deliverability configured properly. Tag-based segmentation for mentors vs. members. Sequences for signup, request submitted, terms agreed, session booked, session completed, follow-up. 5. Handover A short written runbook: how to add a mentor, how to process a deal, how to fix the three things most likely to break. Loom walkthroughs welcome. Must-have Demonstrated hands-on work with the Fluent / WPManageNinja stack. Tell us which plugins and what you built. This is the single biggest factor in who we hire. Strong FluentCommunity configuration: spaces, roles, permissions, member experience. FluentBooking Pro: multi-host setups, permissions, availability, payment gateways, calendar integrations. Fluent Forms Pro: conditional logic, multi-step forms, notifications, integration feeds. FluentCRM: automations, tags, sequences, triggers. Comfortable with small PHP snippets and safe use of a code-snippets plugin — reading a hook, writing five lines, not architecting. Solid HTML/CSS for styling and layout adjustments on top of the plugin UIs. Staging-first discipline, backups before changes, and clear written updates. Nice to have Paymattic or FluentCart. Stripe configuration experience including refunds and disputes. Membership, coaching, or marketplace site experience. WP REST API familiarity (we may expose data later — not part of this scope). Explicitly out of scope Custom plugin development, group mentorship, bidding or auctions, escrow, split payouts, and mobile. Those are a later phase and a different hire. Don't quote for them. How we work Async-first with a weekly call. Tools: Mattermost, Notion, Figma, Google Docs. You'll get written specs. Direction comes from the Director; you execute and flag anything in the spec that can't be built the way it's written — early, not at delivery. To apply Answer these in your cover letter. Generic proposals are declined. Which Fluent / WPManageNinja plugins have you configured, and on what kind of site? Links preferred. Have you set up FluentBooking with multiple independent hosts who manage their own calendars? Describe how you handled host permissions. How would you let a member and a mentor transact at a price they agreed between themselves, using only what FluentBooking and Fluent Forms give you? One paragraph — we want to see how you think, not a perfect answer. Describe something you configured where you deliberately avoided writing custom code, and what you traded away to do it. What's your availability over the next 4–6 weeks? Start your cover letter with the word OASIS.