Contact Us

Have a question, suggestion, or found something that is not working right? Fill in the form below and we will get back to you as soon as we can. We read every message.

Response time: We typically respond within 48–72 hours.

Important Note: We cannot provide custom document templates, individual tax advice, or specific legal counsel under any circumstances.

Your message is sent directly to our team. We do not store form submissions on any server.

Technical Support & Bug ReportsPlease include the tool name, what you expected to happen, and what actually happened. Tell us what problem you are trying to solve — we prioritize feature requests based on what helps the most freelancers.
Business & Press InquiriesFor media requests, partnerships, or business matters, please use the form above and include "Business" or "Press" in the subject line.

Contact Us: Your Comprehensive Hub for Support, Collaboration, and Growth

Welcome to the central nexus for all communications regarding our freelance tools, open-source initiatives, and partnership opportunities. We understand that as an independent professional, your time is your most valuable asset. When you encounter a roadblock, seek a strategic alliance, or want to contribute to the ecosystem, you need clear, actionable, and rapid pathways to the right individuals. This page is meticulously designed to guide you to the exact resources and contacts you need, ensuring zero friction in your journey.

1. How to Get Unmatched Support for Our Freelance Tools

Navigating the complexities of modern freelance workflows requires robust, reliable tools. But even the most elegantly engineered software occasionally presents challenges. Whether you are dealing with a nuanced configuration issue, an unexpected bug, or simply need strategic advice on how to maximize your productivity using our suite, our support infrastructure is architected to deliver precise, swift, and highly effective resolutions. We don't just solve problems; we empower you to master your tools.

Our Multi-Tiered Support Philosophy

We recognize that not all queries are created equal. A minor UI question shouldn't sit in the same queue as a critical workflow-halting bug. To accommodate the diverse needs of our massive user base, we employ a multi-tiered support strategy. This ensures that every user, from the free-tier hobbyist to the enterprise-level agency owner, receives the appropriate level of attention and expertise.

  • Tier 1: Community and Self-Serve Excellence. For immediate answers to common questions, our meticulously maintained knowledge base, video tutorials, and highly active community forums (hosted on Discord and Discourse) are your first line of defense. Here, you tap into the collective wisdom of thousands of seasoned freelancers.
  • Tier 2: Dedicated Technical Support. When self-serve isn't enough, our in-house team of product specialists steps in. These aren't outsourced script-readers; they are power users of our freelance tools who understand the intricate mechanics of your workflows.
  • Tier 3: Engineering Escalation. For deep technical anomalies, edge-case bugs, or API integration complexities, tickets are seamlessly escalated to our core engineering team. This ensures that fundamental flaws are not just patched for you, but resolved for the entire community.

The Pre-Flight Checklist: Before You Submit a Ticket

To help us help you with maximum efficiency, we ask that you run through a brief pre-flight checklist. Taking three minutes to verify these points can often save you hours of waiting and back-and-forth communication.

  • Consult the Official Documentation: Over 85% of standard technical inquiries are fully documented. Use the global search feature in our Docs portal—it's incredibly robust and indexed daily.
  • Check the System Status Page: Are you experiencing latency or connectivity drops? Before troubleshooting your local setup, visit status.freelancekit.dev to ensure there are no ongoing global or regional outages affecting our microservices.
  • Update to the Latest Version: If you are using our desktop clients or CLI tools, ensure you are on the latest stable release. We ship bug fixes weekly, and your issue may have already been resolved in a recent patch.
  • Clear Your Environment Cache: For web-based tools, aggressive caching can sometimes cause anomalous behavior. Perform a hard refresh or clear your application cache and attempt to reproduce the issue.

The Anatomy of a Flawless Support Request

When you do need to reach out, the quality of your initial message directly correlates with the speed of our resolution. Vague reports like "It doesn't work" require our team to play detective, adding unnecessary delays. A pristine support ticket contains specific, actionable intelligence.

When formulating your ticket via our secure portal, please ensure you include the following vital components:

  • A Descriptive, Concise Subject Line: "Error 504 on Invoice Generation via API" is infinitely more helpful than "Help with invoices."
  • Detailed Steps to Reproduce: Provide a meticulous, step-by-step guide on how we can trigger the issue on our end. If we can't reproduce it, we can't fix it.
  • Expected vs. Actual Behavior: Clearly state what you anticipated the software would do, and contrast it with what actually occurred.
  • Environmental Variables: What operating system are you using? Which browser and version? Are you utilizing any third-party extensions that might inject conflicting scripts into the DOM?
  • Rich Media Attachments: A picture is worth a thousand words; a screen recording is worth a million. Attach uncropped screenshots, Loom videos, or console error logs. Visual evidence is paramount.

Service Level Agreements (SLAs) and Expectations

We value transparency above all. Depending on your subscription tier, our response times are guaranteed by strict internal SLAs. Free-tier users can generally expect a response within 48 business hours. Pro-tier subscribers are prioritized within a 12-hour window. Enterprise and Agency partners have dedicated account managers and access to a 24/7 emergency hotline with a 1-hour critical response guarantee.

Regardless of your tier, our commitment remains the same: we will treat your workflow blockages as if they were our own. To initiate a support request now, please navigate to the Help Center portal accessible from your account dashboard, or email support@freelancekit.dev directly from the address associated with your account.

2. Strategic Partnerships and Sponsorship Inquiries

The freelance ecosystem thrives on collaboration, integration, and mutual growth. We are acutely aware that our tools do not exist in a vacuum; they are part of a broader, interconnected digital workspace that independent professionals navigate daily. As such, we are deeply committed to forging strategic partnerships, integrations, and sponsorships that create exponential value for our user base. If you represent an organization, a software platform, or an influential voice in the creator economy, this section outlines how we can build something extraordinary together.

The Anatomy of an Ideal Partnership

We receive hundreds of partnership requests monthly, but we are fiercely protective of our users' experience and data. We do not engage in superficial co-marketing exercises that offer no tangible utility. An ideal partnership with us is characterized by deep technical integration, seamless user experience, and a clear, demonstrable benefit to the freelance community.

We categorize our strategic partnerships into three distinct vectors:

  • Technical Integrations (API & Webhooks): Are you building a financial tool, a CRM, or a project management suite? If integrating our freelance invoicing, time-tracking, or client-management primitives directly into your platform (or vice versa) eliminates friction for mutual users, we want to talk. We offer robust API documentation and dedicated developer support for approved integration partners.
  • Affiliate and Reseller Programs: For agencies, business coaches, and enterprise consultants who actively recommend technology stacks to their clientele, our structured partner program provides lucrative, recurring revenue shares. We equip our affiliates with comprehensive enablement materials, co-branded landing pages, and priority support channels.
  • Content and Educational Collaborations: The modern freelancer is a lifelong learner. If your organization produces high-fidelity educational content—such as masterclasses on tax optimization, legal frameworks for contractors, or advanced client acquisition—we are open to co-hosting webinars, cross-publishing authoritative whitepapers, and sponsoring deep-dive courses that elevate the industry standard.

Sponsorship Opportunities: Aligning Brands with Builders

Our platform is the daily operating system for hundreds of thousands of highly engaged, commercially active freelancers, agencies, and independent creators. This demographic is notoriously difficult to reach through traditional advertising channels, as they employ aggressive ad-blockers and curate their digital environments meticulously.

We offer limited, highly contextual sponsorship opportunities for brands whose products genuinely enhance the independent professional's life. We refuse interruptive banner ads or intrusive pop-ups. Instead, we favor deep, native integrations.

  • Newsletter Sponsorships: Our bi-weekly dispatch, "The Autonomous Professional," reaches over 150,000 double-opted-in subscribers with an astonishing 42% average open rate. We offer one primary sponsor slot per issue, ensuring maximum share of voice.
  • Podcast and Video Integrations: Sponsor our official tutorial series or our interview podcast featuring top-earning freelancers. These sponsorships include bespoke, host-read ad integrations that sound natural and compelling.
  • Event and Hackathon Backing: We regularly host digital hackathons and virtual summits focused on open-source tool creation for freelancers. Sponsoring these events places your brand at the epicenter of innovation, directly in front of the developers and power users shaping the future of work.

How to Pitch Us Successfully

To respect both your time and ours, we ask that all partnership and sponsorship inquiries bypass generic pleasantries and immediately articulate the value proposition. When contacting our growth team, your proposal should concisely address the following critical pillars:

  • The Mutual Value Hypothesis: Exactly how does this partnership benefit our users, your users, and both of our bottom lines? Quantify the expected impact wherever possible.
  • Technical Feasibility (If Applicable): If proposing an integration, have your engineering lead review our public API first. Provide a high-level architectural overview of how the systems will interact.
  • Resource Requirements: What do you need from us to make this successful? Be specific about engineering hours, marketing bandwidth, or financial commitments.
  • Go-to-Market Strategy: A technical integration is only as good as its distribution. Outline how we will jointly launch and promote this partnership to ensure maximum adoption.

Vague emails requesting a "quick 15-minute sync to explore synergies" are routinely archived. Proposals that demonstrate deep research into our product ecosystem and present a compelling, asymmetric upside will be escalated to our executive team immediately.

Please direct all meticulously crafted partnership proposals to partnerships@freelancekit.dev. Include [Partnership Proposal] and your company name in the subject line to ensure routing past our automated filters. Our business development team reviews these submissions on a weekly basis, and you can expect a definitive answer—or a request for a follow-up technical call—within 7 to 10 business days.

3. Contributing to Our Open-Source Toolkit

The foundation of our platform is inextricably linked to the open-source movement. We firmly believe that the tools powering independent, decentralized work should themselves be built in a decentralized, transparent, and collaborative manner. While our core enterprise infrastructure remains proprietary to ensure security and scalability, a vast array of our CLI tools, UI component libraries, formatting parsers, and utility plugins are fully open-source, governed by MIT and Apache 2.0 licenses.

We invite developers, technical writers, UI/UX designers, and quality assurance engineers from across the globe to contribute to our repositories. Your code has the potential to optimize the workflows of millions of freelancers. This section outlines our philosophy on open-source contributions, the architecture of our repositories, and the exact protocols for getting your pull requests merged smoothly.

Why Contribute to the FreelanceKit OSS Ecosystem?

Contributing to open-source software (OSS) is a significant investment of your personal time and cognitive bandwidth. We do not take this lightly. In return for your expertise, we have engineered an environment designed to provide immense reciprocal value:

  • Architectural Mentorship: Every single Pull Request (PR) is reviewed by our senior staff engineers. You will receive incredibly detailed, constructive feedback on your code, focusing on performance, security, and adherence to modern design patterns. It is an unparalleled opportunity to upskill.
  • Public Attribution and Portfolio Building: Meaningful contributions are permanently etched into our commit history. Furthermore, significant contributors are highlighted in our release notes, our monthly newsletter, and on our core contributors page—a massive signal of competence to potential clients or employers.
  • Bounty Programs for Critical Infrastructure: While we cherish voluntary contributions, we also believe in equitable compensation for high-impact work. We regularly attach monetary bounties (via platforms like GitHub Sponsors or Polar) to complex, high-priority issues within our issue trackers.
  • Shaping the Future of Freelance Tech: By contributing code, you aren't just fixing bugs; you are directly influencing the technological trajectory of tools that freelancers rely on daily to run their businesses.

Getting Started: The Path from Fork to Merge

To maintain the stability and security of our ecosystem, we employ a rigorous but highly predictable contribution pipeline. Before you write a single line of code, we ask that you familiarize yourself with our fundamental guidelines.

Step 1: Discovering the Right Issue

Navigate to our primary GitHub organization. We utilize a highly organized tagging system. If you are a newcomer, filter the issues by the good first issue or help wanted labels. These tasks have been specifically vetted by our core team as having a clear scope, low architectural risk, and high immediate utility. Avoid tackling massive refactors or unassigned major features without first opening a discussion thread.

Step 2: The Pre-Code Consensus

Communication precedes computation. Before investing hours into a solution, comment on the issue you wish to tackle. Briefly outline your proposed approach, the libraries you intend to utilize, and any edge cases you anticipate. A maintainer will usually respond within 24 hours to green-light your approach, ensuring you don't waste time building something that fundamentally conflicts with our long-term roadmap.

Step 3: Development and Adherence to Standards

Fork the repository and clone it locally. Our repositories are equipped with comprehensive CONTRIBUTING.md files. These documents dictate our strict linting rules (we heavily utilize Prettier and ESLint), our testing requirements (we expect a minimum of 85% test coverage for new logic via Jest or Playwright), and our commit message taxonomy (we strictly adhere to Conventional Commits format, e.g., feat(parser): add support for ISO-8601 dates).

Step 4: Submitting the Pull Request

When submitting your PR, our automated CI/CD pipelines (powered by GitHub Actions) will immediately run a gauntlet of tests, type checks, and security scans. Ensure your PR description utilizes our template, linking to the original issue (e.g., Resolves #402) and providing a clear, concise summary of the architectural decisions made. If the CI fails, please address the errors before requesting a human review.

Beyond Code: Non-Technical Contributions

Open source is a holistic endeavor. If your expertise lies outside of writing TypeScript or Rust, your contributions are still immensely valuable.

  • Documentation and Localization: Clear, precise documentation is the lifeblood of adoption. We constantly need technical writers to refine our API docs, write conceptual tutorials, and translate our user interfaces into multiple languages.
  • UX/UI Design: If you spot accessibility flaws, confusing user flows, or inconsistent design tokens, we welcome design-focused PRs. Submitting Figma files or proposing CSS/Tailwind refinements is highly encouraged.
  • Community Triage: Simply helping us organize our GitHub issues—identifying duplicates, requesting reproduction steps from users, and categorizing bugs—is a massive force multiplier for our core team.

Ready to leave your mark? Head over to github.com/freelancekit-oss to explore our active repositories. For overarching discussions about the direction of our open-source efforts, join the #oss-development channel in our community Discord. Let's build the ultimate toolset for the modern freelancer, together.

4. A Masterclass in Cold Emailing: Best Practices for Contacting Us (and Anyone Else)

As a platform dedicated to freelance success, we receive thousands of cold emails every week—pitches for guest posts, requests for software integration, inquiries from job seekers, and solicitations for B2B services. The stark reality is that 95% of these emails fail spectacularly. They are ignored, deleted, or funneled directly into spam algorithms.

However, the 5% that break through the noise are masterclasses in digital communication. Because cold outreach is a foundational skill for any freelancer seeking clients, we have decided to turn this section of our Contact page into a comprehensive, actionable mini-guide. Whether you are emailing our executive team to propose a partnership, or emailing a Fortune 500 prospect to pitch your freelance services, adhering to these advanced principles will exponentially increase your response rates.

Principle 1: Radical Relevance and Deep Personalization

The era of spray-and-pray email blasts is dead, buried by sophisticated spam filters and human exhaustion. An effective cold email must demonstrate that you have done extensive, non-trivial research on the recipient.

  • Faux Personalization Fails: Simply inserting {{firstName}} and {{companyName}} via a mail-merge tool is not personalization; it is baseline formatting. Decision-makers can spot an automated sequence from the first sentence.
  • Deep Personalization Wins: Genuine relevance means referencing a specific podcast they recently appeared on, a nuanced point from their company's latest quarterly report, or a recent product feature they shipped. For example: "I noticed in your recent changelog that you rebuilt the invoice rendering engine. That must have been a massive refactor. I specialize in optimizing PDF generation microservices..." This proves you are a human who is paying attention, instantly earning you the right to their time.

Principle 2: The Art of the Subject Line

Your subject line has a single, ruthless job: to get the email opened without triggering psychological spam filters. It should not summarize the entire email, nor should it rely on clickbait tactics that destroy trust upon opening.

Terrible Subject Lines
  • "Quick question for you!" (Vague, widely used by spammers)
  • "10x your freelance platform's revenue today" (Hyperbolic, unbelievable)
  • "Following up on my previous message" (Guilt-inducing, annoying)
Excellent Subject Lines
  • "Question about the caching logic on your new API endpoints" (Specific, technical, implies value)
  • "Idea for the upcoming FreelanceKit Q3 launch" (Timely, relevant)
  • "Re: Your tweet about managing asynchronous state" (Contextual, ego-stroking)

Principle 3: Brutal Brevity and Formatting for Skimmability

Assume the recipient is reading your email on a mobile device while walking to a meeting, running on four hours of sleep. If they see a solid wall of text stretching down the screen, they will archive it instantly. Cognitive load is your enemy.

  • The 150-Word Limit: Force yourself to edit your pitch down to 100-150 words. Every sentence must fight for its life. Remove filler phrases like "I hope this email finds you well" or "My name is X and I work at Y." (They can see your name in the "From" field and your company in your signature).
  • Visual Hierarchy: Use extremely short paragraphs—no more than two or three lines. Utilize bold text judiciously to highlight core metrics or the exact value proposition. Bullet points are highly effective for breaking down complex ideas quickly.

Principle 4: Leading with Value, Not Requests

The most catastrophic mistake in cold outreach is making the email about you and what you want. "I am looking for clients," "I want to feature my product on your blog," "Can I have 15 minutes of your time?" These are transactional withdrawals from a bank account with a zero balance.

Instead, lead with an asymmetric deposit. Provide immense upfront value with zero expectations.

Example of Leading with Value:

"I noticed the mobile loading speed on your pricing page drops to a 65 on Google Lighthouse due to unoptimized hero images. I took the liberty of compressing them using modern WebP formats and creating a custom script to lazy-load them below the fold. Here is a link to the assets and the code snippet. You can implement it in 5 minutes and it should push your score back into the 90s."

When you provide undeniable value before ever asking for a meeting, the dynamic completely shifts. You transition from a nuisance to an asset.

Principle 5: The Frictionless Call to Action (CTA)

Never ask a busy person to do the heavy lifting of scheduling. Asking "What does your calendar look like next week?" forces them to cross-reference schedules, formulate a response, and engage in logistical ping-pong.

Instead, use an incredibly low-friction, specific Call to Action. The "Interest-Based CTA" is often the most effective. Instead of asking for time, ask for interest: "Are you open to exploring this further?" or "Is this a priority for your team this quarter? If so, I can send over a 2-minute Loom video walking through the architecture." This requires a simple "Yes" or "No" reply, drastically increasing your chances of engagement.

If you are emailing us using these principles, you are already in the top 1%. We look forward to reading your brilliantly crafted messages.

5. Frequently Asked Questions: The Ultimate Knowledge Repository

Before routing your inquiry to our support engineers or business development teams, we highly encourage you to review this comprehensive FAQ section. We have meticulously aggregated, analyzed, and answered the most common—and critically, the most complex—questions posed by our global user base. This isn't a superficial list; these are deep, authoritative answers designed to unblock your workflow instantaneously.

Q1.How does the data migration process work if I am transitioning from a legacy platform?

Transitioning your entire freelance business infrastructure—clients, invoices, project history, and tax records—is a high-stakes operation. We treat data integrity as our absolute highest priority. Our proprietary migration engine utilizes a deterministic, transactional import process. We natively support CSV, JSON, and direct API-to-API migrations from all major legacy platforms (including Upwork, Fiverr, QuickBooks, and FreshBooks).

When you initiate an import, the system first maps your schema to ours in an isolated sandbox environment. It runs a pre-flight validation check to flag any anomalous data types or orphaned records. Once you approve the mapping, the migration executes. Crucially, this process is non-destructive and fully reversible; you can roll back the entire migration within 14 days without corrupting your existing datasets.

Q2.What are the exact technical specifications and rate limits of your public API?

Our RESTful API is built on edge-computed microservices, ensuring ultra-low latency globally. It strictly adheres to OpenAPI 3.0 specifications. Authentication is handled via secure, scoped bearer tokens utilizing OAuth 2.0.

Regarding rate limiting: we employ a dynamic token bucket algorithm. For Free-tier users, the limit is strictly capped at 100 requests per minute per IP address. Pro-tier users are granted 1,000 requests per minute, and Enterprise partners enjoy virtually uncapped throughput, subject only to fair-use infrastructure protections. We provide sophisticated response headers (X-RateLimit-Limit, X-RateLimit-Remaining, and X-RateLimit-Reset) on every request, allowing you to programmatically throttle your own scripts to avoid HTTP 429 (Too Many Requests) errors.

Q3.Are you SOC 2 compliant, and how do you handle client payment data?

Yes. We maintain strict SOC 2 Type II compliance, audited annually by independent, third-party security firms. We understand that as a freelancer, you are entrusting us with highly sensitive PII (Personally Identifiable Information) and financial records.

When it comes to payment data, we utilize a zero-trust, tokenized architecture. We never store raw credit card numbers or bank account details on our servers. All financial transactions are processed securely via our PCI-DSS Level 1 compliant partners (Stripe and PayPal). When a client pays an invoice through our platform, the data is encrypted via TLS 1.3 in transit and AES-256 at rest. Our infrastructure is continuously scanned for vulnerabilities, and we maintain an active, lucrative bug bounty program on HackerOne to crowdsource security auditing.

Q4.How does the automated tax categorization algorithm function?

Our platform includes an intelligent expense tracking module designed to eliminate the anxiety of tax season. The categorization engine leverages a specialized, fine-tuned machine learning model (based on a transformer architecture) trained on millions of anonymized, legally compliant expense datasets across various global tax jurisdictions.

When you connect your business bank account via Plaid or upload a receipt, OCR (Optical Character Recognition) extracts the merchant, date, and amount. The model then analyzes the merchant name and contextual metadata to predict the correct tax category (e.g., "Software Subscriptions," "Travel," "Hardware Depreciation") with an accuracy rate exceeding 94%. Furthermore, the model continuously learns from your manual corrections, creating a highly personalized categorization matrix that adapts to your specific niche over time.

Q5.Can I white-label the client portal and invoice documents?

Brand consistency is paramount for premium freelancers and agencies. We offer extensive white-labeling capabilities exclusively for our Pro and Enterprise tiers. You are not limited to simply uploading a logo.

Our theming engine allows you to inject custom CSS to completely reskin the client-facing portal. You can map the portal to your own custom domain (e.g., clients.youragency.com) complete with automatically provisioned SSL certificates. For document generation, we provide a visual drag-and-drop builder as well as a raw HTML/Liquid templating environment. This allows you to construct invoices, proposals, and contracts that perfectly mirror your brand's typographic and layout standards, entirely removing any reference to our underlying platform.

Q6.What happens to my data if I decide to cancel my subscription?

We believe in software sovereignty. Vendor lock-in is an unethical practice that we vehemently oppose. If you choose to offboard from our platform, you maintain absolute ownership and control of your data.

Upon initiating an account deletion, you will be prompted to trigger a comprehensive data export. This generates an encrypted, single-file archive (ZIP) containing all your invoices (in PDF and JSON formats), client databases, time logs, and system configurations. Once the export is confirmed, your account enters a 30-day "soft delete" phase, allowing for emergency recovery. After 30 days, your data is permanently, cryptographically scrubbed from our primary databases and all rolling backups, in strict adherence to GDPR "Right to be Forgotten" mandates.

Q7.Do you offer custom SLA agreements and dedicated account managers for large agencies?

Yes, our Enterprise offering is specifically engineered for high-volume agencies, talent marketplaces, and large-scale digital collectives. We recognize that off-the-shelf solutions often fail to meet the complex governance and operational requirements of larger entities.

Enterprise clients receive a heavily customized Service Level Agreement (SLA) guaranteeing 99.99% uptime, with substantial financial penalties (service credits) if we fail to meet these metrics. Furthermore, you are assigned a dedicated Customer Success Engineer (CSE). Your CSE acts as an internal advocate, providing architectural guidance, conducting quarterly business reviews, and establishing a direct, private Slack or Microsoft Teams channel with our core engineering team for rapid deployment of necessary custom features.

Q8.How do you handle feature requests, and what does your product roadmap look like?

Our product evolution is entirely driven by user velocity and workflow friction. We maintain a radically transparent, public-facing roadmap accessible at roadmap.freelancekit.dev.

Feature requests can be submitted directly through your user dashboard. These requests enter our triage system, where they are categorized and opened up for community voting. The product management team reviews the top-voted features bi-weekly. If a feature aligns with our core vision and technical feasibility constraints, it is moved to the "Planned" column. We update the roadmap dynamically, providing detailed technical briefs and estimated delivery timelines for features in the "In Progress" phase, ensuring you always know exactly what is being built and when it will ship.