Frequently Asked Questions

Common questions about working with Stackiv.

Time Zones & Communication

What time zones do you work in?

Our core team operates in IST (UTC+5:30), with committed overlap hours for US Eastern (typically 9am–1pm EST) and European time zones (1pm–5pm CET). We structure our workday to ensure real-time collaboration windows when needed.

How do you handle async communication?

We use your existing tools (Slack, Linear, Notion, Jira) and maintain clear written documentation. Updates are posted at the end of our day so you have context at the start of yours. We don't expect immediate responses - async discipline is built into how we work.

What communication tools do you use?

We adapt to your stack. Most clients use Slack for communication, Linear or Jira for project tracking, and Notion or Confluence for documentation. We don't force you onto new tools.

Team Structure & Process

How long does onboarding take?

Typically 1–2 weeks for engineers to get up to speed on your codebase, tools, and workflows. This includes architecture review, local setup, and initial contribution. We aim for meaningful commits in week one.

How are engineers vetted?

Engineers go through technical evaluation (live coding, architecture discussion, past work review), communication assessment (written and verbal), and reference checks from previous engagements. We don't hire from a bench - we work with people we've collaborated with before.

Can we scale the team up or down?

Yes. Team size adjusts based on project phase and priorities. Discovery might be 1–2 engineers. Active build might be 3–5. Post-launch support might drop to 1. We structure engagements to flex with your actual needs.

What if something isn't working?

We address it directly. If there's a communication issue, skill mismatch, or delivery concern, we discuss it transparently and adjust. If an engineer isn't the right fit, we replace them. No excuses, no bureaucracy.

Engagement & Pricing

What's the minimum engagement duration?

We prefer minimum 3-month engagements for embedded teams (allows time to build context and deliver meaningful work). Project-based work varies - could be 6–12 weeks depending on scope. We don't do one-week consulting gigs.

What's a typical engagement length?

Most clients work with us for 6–18 months. Some are ongoing multi-year relationships. It depends on whether you need a specific project delivered or long-term team augmentation.

How is pricing structured?

Monthly retainer based on team size and scope. Pricing is transparent and fixed per month - no surprise invoices. We can structure fixed-price projects for well-defined work, but most engagements are time-based with clear deliverables.

What's the project minimum budget?

Realistic minimum is $10k/month for one senior engineer. Most engagements start around $20k–30k/month for a small team. If your budget is under $10k/month, we're likely not the right fit.

Legal & IP

Who owns the IP?

You do. All code, designs, and deliverables created during the engagement belong to you. This is standard in our contracts - no shared ownership or licensing complications.

Do you sign NDAs?

Yes, we sign mutual NDAs before any detailed technical discussions. Standard practice.

Post-Engagement

What happens after the project ends?

We provide handoff documentation, knowledge transfer sessions, and typically offer a support window (1–3 months) for questions as your team takes over. We don't disappear the day the contract ends.

Do you offer ongoing support after delivery?

Yes. Many clients keep a reduced team (1 engineer) on retainer for maintenance, bug fixes, and small enhancements. We can structure flexible support arrangements.

Still have questions?

Let's talk directly. We respond within 1 business day.

Get in Touch