Private Small Launch Resource
This legacy page stays live for old links and community referrals. It is application-only, low priority, and not part of the main FunkPd rescue, rebuild, stabilization, systems, or support path.
01 // Private_Path
01
Legacy access
This page remains available for old links, prior conversations, and selected community referrals.
Private
Resource
Resource
02
Priority
Small launch requests wait behind urgent fixes, fragile-site recovery, rebuilds, stabilization, and systems work.
Low
Priority
Priority
03
Scope
Only simple brochure work is considered. No broken sites, custom systems, rescue work, or business-critical rollout risk.
Simple
Only
Only
04
Acceptance
Nothing is promised until the request is reviewed, accepted, scoped, and priced in writing.
Written
Scope
Scope
02 // Fit
IN
Community or referral request
Best for a known referral, local community request, or old conversation where a very small site is enough.
Ideal
Fit
Fit
IN
Simple inputs
The request is clear, the content is ready, and there is no fragile technical stack to untangle.
Ideal
Fit
Fit
OUT
Business-critical site
If downtime, revenue, staff workflows, or reputation are at risk, use the rescue, rebuild, stabilization, or systems path.
Not a
Fit
Fit
OUT
Custom or complex work
Carts, logins, memberships, booking systems, integrations, migrations, and custom workflows are separate services.
Not a
Fit
Fit
03 // How_Requests_Are_Handled
Step 1
Fit check
Send the request with context, timeline pressure, and what already exists.
Input
Phase
Phase
Step 2
Private review
If it is not a fit, it will be routed to the right current service or declined.
Production
Station
Station
Step 3
Written scope
Accepted requests get a narrow written scope and price before work starts.
Quality
Lock
Lock
Step 4
Small delivery
Delivery stays inside the approved scope. Larger needs become a separate current service.
Fixed
Scope
Scope
Step 5
Handoff
Access, ownership notes, and basic launch proof are handed back cleanly.
Handoff
Complete
Complete
04 // Handover
KEYS
Ownership
If accepted, access and ownership notes are handed back in your name.
Full
Access
Access
NO
No priority support
This is not a support plan. Fragile or urgent sites should start with a current rescue or stabilization scope.
Current
Service
Service
NEXT
Expansion
SEO, extra pages, integrations, and bigger systems are separate current services.
Phase
Transition
Transition
Looking for the main buyer path? Use the service map or current pricing.
Contact
Site URL, goal or problem, urgency, access, platformDirect Details
Contact channelsEmail
Phone
Facebook Messenger
Instagram (DM)
Threads (DM)
X / Twitter (DM)
LinkedIn (Nolan)
LinkedIn (Company)
Office
521 Washington Ave, Winnipeg, MB R2K 1M1, Canada
Hours
Support is handled by fit and urgency. Emergency routing is for real outages only.
Response Time
Replies within 24 hours. Priority response is reserved for active Site Ops clients and true outages.
Socials
Socials monitored for inquiries; support via email only.
Privacy
Form data is used only to reply and scope work. See our Privacy Policy.
