FAQ
Common questions about working with CHICROSS STUDIO.
Scope & Services
What types of projects do you take on?
We focus on web development, workflow automation, system integration, and document processing. Projects range from corporate websites to complex multi-system automation pipelines. We're best suited for work that benefits from engineering rigor and clear specifications.
Do you handle design work?
We handle implementation—turning designs into functional systems. We don't provide original graphic design, branding, or visual identity work. If you have design assets, we can implement them. If you need design services, we can recommend partners.
Can you work with existing systems?
Yes. Many engagements involve integrating with or extending existing infrastructure. We assess integration complexity during scoping and document any dependencies on external systems.
Do you build mobile apps?
Our focus is web applications and backend systems. For native mobile development, we recommend specialized mobile development partners. We do build responsive web applications that work well on mobile devices.
Process & Timeline
How long does a typical project take?
It varies significantly by scope. A focused automation project might take 4–8 weeks. A comprehensive web platform could take 3–6 months. We provide timeline estimates during scoping, always with acknowledgment of unknowns.
How do you handle changing requirements?
Through documented change management. Minor clarifications happen naturally. Significant scope changes are assessed for impact, documented, and require explicit approval before implementation. This protects both parties.
What's your communication style?
Regular async updates (typically weekly), sync checkpoints at milestones, and ad-hoc availability for urgent questions. We're responsive during business hours and clear about response time expectations.
What if we need to pause a project?
We can accommodate pauses with advance notice. We document current state thoroughly so work can resume cleanly. Extended pauses may require context-restoration time when resuming.
Deliverables & Handoff
What do we receive at the end?
At minimum: source code, deployment artifacts, and documentation. Specifics depend on project type, but typically include deployment guides, operations runbooks, architecture notes, and change logs.
Who owns the code?
You do. Upon project completion and final payment, all work product transfers to you. We don't retain ownership or licensing claims on custom work built for you.
Can we maintain the system ourselves after handoff?
That's the goal. We document everything needed for ongoing maintenance. We also offer optional iteration support if you prefer continued involvement.
What format is the code in?
Version-controlled source code (typically Git), with clear project structure and documentation. We follow standard practices for the technologies involved.
Quality & Reliability
How do you ensure quality?
Multiple layers: code review, testing (where appropriate for the project type), documentation review, and structured handoff. For complex projects, we apply our research methodology—defining success criteria upfront and measuring against them.
What if something doesn't work as expected?
Issues within the agreed scope are fixed at no additional cost. We distinguish between genuine defects (our responsibility) and new requirements (scope change process). The scope document is the reference for these determinations.
How does your research approach improve delivery?
Applied research means we've tested techniques before applying them to your project. We know the boundaries and failure modes. Evaluation methodology means we measure outcomes rather than just declaring success.
Confidentiality & Security
How do you handle confidential information?
With appropriate care. We can sign NDAs where required. We use secure communication channels and limit access to project materials. We don't share client details or project specifics without explicit permission.
Do you store our data?
Only what's necessary for the project. Development typically involves working with realistic data structures, sometimes sanitized production data. We don't retain client data after project completion unless explicitly arranged for ongoing support.
Can you work with regulated industries?
We have experience with projects in regulated contexts. Specific compliance requirements should be discussed during scoping so we can assess fit and plan appropriately.
Getting Started
How do we start?
Contact us with a brief description of your project. We'll schedule an initial conversation to understand your needs and assess whether there's a good fit.
What should we prepare for the first conversation?
The more context you can provide upfront, the more productive the conversation:
- What problem are you trying to solve?
- What have you tried already?
- What does success look like?
- Any timeline constraints?
- Relevant references or examples?
What if we're not sure exactly what we need?
That's common. The initial conversation is exploratory. We can help you refine the problem definition and identify what kind of solution might work. No commitment required for this discussion.
Other Questions
Are you available for short consulting calls?
For established clients or clearly scoped discussions, yes. For general advice-seeking, we typically fold this into proper scoping conversations where we can provide meaningful guidance.
Do you work with agencies or other service providers?
Occasionally, as a specialized implementation partner. We're clear about role boundaries and communication expectations in these arrangements.
What's your availability?
We take on limited concurrent engagements to maintain quality. If we don't have immediate capacity, we'll be honest about timeline and can discuss scheduling for future starts.
Still have questions? Contact us directly.