How We Work

Everything you need to know about working with us

From first conversation through delivery and beyond — purpose-built software, AI-assisted development, fixed pricing, and 50/50 payment terms.

Our Process

From first call to launch

130 min

Discovery Call

We learn about your situation: what’s working, what’s not, and where you think you need help. No pitch — just listening. By the end, we’ll both know whether this is worth pursuing.

245 min

Technical Scoping

We bring in our dev lead to dig into your systems, data, workflows, and requirements. We’ll map out what needs to be built at a level of detail that lets us quote accurately.

35–7 business days

Proposal

You receive a fixed-price proposal with three options — Essentials, Recommended, and Full Build — so you can choose the scope that fits your budget and priorities. Each option includes a clear scope, timeline, and price.

4Week 1

Kickoff

Once you sign off and submit the first payment, we lock in your project slot, assign your team, and map out the build in detail. You’ll know exactly what’s happening and when.

5Weeks 2–X

Build Sprints

We work in focused 1–2 week sprints with demos at each milestone. You see real, working software throughout the process — not just mockups or promises. Feedback is incorporated as we go.

6Final week

Delivery & Handoff

We deploy to your environment, train your team, and hand over full source code and documentation. You own everything. 30 days of post-launch bug-fix support is included.

About Foxworks

What does Foxworks Technologies actually do?

We build purpose-fit software. That means custom applications designed specifically around how your business operates — not generic tools you have to reshape your process around.

Our sweet spot is replacing fragile multi-tool setups, eliminating manual workflows, and building the internal tools that give companies a real operational edge.

What do you mean by "AI-assisted development"?

We use AI agents throughout our development process to handle repetitive tasks like scaffolding, boilerplate code, testing, and documentation. This lets our senior engineers focus on the parts that matter most: architecture, business logic, security, and quality.

The result is that we deliver custom software at a speed and cost that would have been impossible even a year ago. You get the benefits of a large team without the overhead of one.

To be clear: AI assists our engineers — it doesn’t replace them. Every line of code is reviewed, tested, and owned by experienced humans.

How big is your team?

We’re a lean, senior team by design. You work directly with the people building your software — no account managers, no layers of project management between you and the work. When you have a question, you’re talking to the person who can answer it.

What industries do you work with?

We’re industry-agnostic but tend to work with companies that have complex operational workflows — financial services, professional services, logistics, healthcare operations, and B2B SaaS companies that need internal tools. The common thread isn’t the industry; it’s the problem: you’ve outgrown your current tools and need something built for how you actually work.

Pricing & Payment

How does your pricing work?

We’re a value-priced firm, which means we charge a fixed price for a defined scope of work. No hourly billing, no time tracking, no surprise invoices. You know exactly what you’re paying before we start.

We price based on the value the software delivers to your business, not on how many hours it takes us to build it. This aligns our incentives: we’re motivated to deliver great work efficiently, not to drag things out.

What are your payment terms?

Our standard terms are 50/50: half upfront to kick off the project, half on delivery. The first payment secures your project slot and funds the initial build phase. The second payment is due when we deliver the final product and you sign off on it.

This structure protects both sides. You’re never more than 50% committed at any point, and we’re incentivized to deliver on time because we don’t collect the second half until you’re satisfied.

How much does a typical project cost?

It depends entirely on the scope. Our projects typically range from $15K for a focused, single-purpose tool to $150K+ for a comprehensive platform with multiple integrations and user types.

Every proposal includes three options at different price points, so you can choose the scope that fits your budget. Many clients start with the Essentials option and expand later once they see the ROI.

Why three options instead of one price?

Because the right scope depends on where you are right now. Some companies need the full vision on day one. Others are better served by starting with the essentials, proving the value, and expanding from there.

Three options give you that flexibility. And because you helped define the layers during our scoping conversations, each option maps directly to what you told us you need.

Do you charge for the discovery and scoping calls?

No. Everything before the proposal is free. The discovery call, the technical scoping call, and the proposal itself are all on us. You don’t pay anything until you’ve seen exactly what we’d build, how long it would take, and what it would cost — and you’ve decided to move forward.

The Build

How long does a typical project take?

Most projects are delivered in 4–12 weeks, depending on scope. The Essentials tier of a project might ship in 4–6 weeks, while a Full Build with complex integrations and multiple user types might take 10–12 weeks.

We’ll give you a specific timeline in the proposal, and we stick to it. If anything changes, you’ll know immediately and we’ll agree on a new timeline together.

What if our requirements change during the build?

Minor adjustments within the agreed scope are expected and included. That’s why we work in sprints with regular demos — so we can course-correct as you see the product take shape.

If you need something significantly beyond the original scope, we’ll have a transparent conversation about it. We can adjust the current engagement or scope a follow-on phase. Either way, you’ll know the cost before any new work begins.

How much of my team’s time does this require?

Typically 2–3 hours per week from your designated point of contact. That covers answering our questions, reviewing demos, and providing feedback at each milestone.

We front-load the heavy collaboration in the first week or two when we’re aligning on requirements and architecture. After that, your time commitment drops to quick reviews and occasional check-ins.

What tech stack do you use?

We’re stack-flexible and choose the technology that best fits the problem, not the other way around. During the technical scoping call, our dev lead will recommend a stack based on your specific needs, existing systems, and long-term goals. If you have a preferred technology or existing infrastructure, we’re happy to work within those constraints.

Can I see progress during the build, or do I wait until the end?

You see working software every 1–2 weeks. Every sprint ends with a demo of real, functional features — not mockups or slides. You provide feedback, we incorporate it, and we move to the next sprint. This means issues are caught early, not at the eleventh hour.

Ownership & After Delivery

Who owns the code?

You do. 100%. Upon delivery and final payment, you receive full ownership of the source code, documentation, and all project assets. It lives in your repository, on your infrastructure, under your control. There’s no licensing, no recurring fees for using what we built, and no lock-in. If you decide to part ways, any competent developer can pick up the codebase and continue working with it.

What happens after you deliver? Who maintains it?

Three options, depending on what makes sense for your team:

Self-maintain: We hand over clean, documented code. Your internal team (or any developer you hire) can maintain and extend it without us.

Ongoing support retainer: Most clients start with a small monthly retainer that covers bug fixes, minor updates, and on-call support. This is the most common path right after launch.

Phase 2 engagement: If you started with the Essentials tier and want to expand, we scope a follow-on project at a new fixed price.

What’s included in the 30-day post-launch support?

Every project includes 30 days of bug-fix support after delivery at no additional cost. If something we built isn’t working as specified, we fix it. This covers defects within the agreed scope — not new features or scope changes. After the 30-day window, ongoing support is available through a retainer arrangement.

What if Foxworks goes away? Are we stuck?

No. We build specifically to avoid vendor lock-in. You own the code from day one. It’s in your repository, well-documented, and written using standard technologies that any qualified developer can work with. We don’t use proprietary frameworks, obscure dependencies, or custom tooling that would tie you to us. The goal is to build you an asset, not a dependency.

Do you host the software?

We deploy to your infrastructure or help you set up hosting, but we don’t act as the hosting provider. This is intentional — we don’t want to be a bottleneck or a recurring cost center for something as straightforward as hosting. During the build, we’ll recommend the most cost-effective hosting setup for your needs and handle the deployment. Ongoing hosting costs are your responsibility and typically run $20–500/month depending on scale.

Getting Started

How do I know if custom software is the right move for us?

Custom software makes sense when at least one of these is true:

You’re paying for SaaS tools but only using 20–30% of the features. Your team spends significant time on manual workarounds or moving information between systems. Your workflow doesn’t fit neatly into any off-the-shelf product. You need a competitive edge that can’t come from tools everyone else also has access to. You’ve tried to make existing tools work and you’ve hit a wall.

If none of these resonate, SaaS might genuinely be the better path — and we’ll tell you that honestly on the first call.

What’s the first step?

A 30-minute discovery call. No prep needed on your end — just come ready to talk about what’s working and what isn’t. We’ll ask questions, listen, and tell you honestly whether we think we can help. If it’s a fit, we schedule a technical scoping call with our dev lead. If it’s not, we’ll tell you and point you in the right direction.

How quickly can you start once we sign off?

Typically within 1–2 weeks of receiving the first payment. We’ll confirm your project start date in the proposal, and the kickoff meeting is usually scheduled for the first day of your slot. If you have a hard deadline, let us know early — we can sometimes adjust scheduling to accommodate urgent timelines.

Ready to talk?

Schedule a discovery call — no commitment, no pitch deck, just a real conversation.