STRAIGHT ANSWERS BEFORE YOU SAY YES.

We design the product around your requirements, workflows and agreed design direction. Reusable SCS architecture supports delivery; it does not substitute a generic template for the product you commissioned.

Your product, built with precision and delivered in seven days. Risk-free: if we miss the deadline or it does not match your expectations, you receive a full refund.

Written expectations guide the design and implementation. Complete workflow tests, deployment checks and acceptance make the finished result reviewable. Precision is a delivery standard, not a claim that software can never have a defect.

Our offer covers bespoke software across applications, platforms, automation, AI and connected systems. We review your requirements and external dependencies before accepting a start date. Any software describes our capability; it does not mean unknown dependencies or third-party approvals are already resolved.

The offer is a deployed bespoke product matching your expectations, not an automatic reduction to an MVP. The written scope specifies what finished means for your commission, including the workflows to be tested.

Seven calendar days. The clock starts when payment, final written approval and the required system access are in place, as confirmed in your project agreement.

Seven calendar days, not seven working days. The project agreement records the start conditions and date so both sides can see the same delivery commitment.

A deployed application that meets the expectations recorded before the build, with the agreed end-to-end workflows tested. A demo or a handover document on its own is not the promised finished product.

The team confirms current availability and your start date directly. The website does not reserve a slot or publish an unverified live capacity count.

If we miss the agreed seven-day deadline or the product does not match your expectations, you receive a full refund of the development fee. We agree your expectations in writing before the build: the workflows, design direction and outcomes the product must deliver. Acceptance tests make those expectations checkable; they do not replace the promise to meet them.

If we miss the agreed seven-day deadline or the product does not match your expectations, you receive a full refund of the development fee.

Email sales@spacecodestudios.com with your project reference and the deadline or expectations that were not met. The team handles the request directly. Confirm payment processing, hosting, licence and handover arrangements in your written agreement; the FAQ cannot decide a claim or promise a processing date.

We agree your expectations in writing before the build: the workflows, design direction and outcomes the product must deliver. Acceptance tests make those expectations checkable; they do not replace the promise to meet them.

Your development price is fixed against your requirements before the build starts. A complete scope review returns a proposal within 48 hours, including the monthly licence and operating commitment. The calculator is an illustration, not a quote.

Yes. The development price is agreed against your requirements before the build. Changes need a written agreement rather than an unexpected additional charge. The operating licence is separate and belongs in the proposal.

Payment and final written approval are part of the agreed start conditions. The team provides the invoice and payment arrangements with your proposal. This FAQ does not collect payments or publish an unconfirmed deposit schedule.

The development fee and monthly licence are separate in the existing service model. Your proposal should identify hosting, support and any external provider charges so you can review the full commitment before approval.

No. It models potential hours and productivity value using adjustable assumptions. Its investment figures are illustrative, not a current price list or guaranteed cash saving. A project-specific proposal is the basis for a buying decision.

The existing SCS model is a licensed service rather than a code handover. Your proposal should explain rights to your application, the underlying architecture and your data. If you need outright ownership, raise it before commissioning; do not assume a website enquiry changes the licence.

You licence the software and SCS architecture monthly. The existing service model has a twelve-month minimum after successful deployment. Maintain keeps the agreed application working; Improve includes a scoped frontend change allowance; Evolve includes scoped full-stack changes. Unused allowances do not roll over. Your written proposal sets out the included service and full commitment.

Agree data ownership, permitted access, exports and retention in the project agreement. Software licensing and rights to business data are different questions. Do not send passwords or sensitive customer datasets in the enquiry form.

Ask for the termination, data export, hosting and handover arrangements in writing before approval. They depend on your agreement. This FAQ cannot promise source-code transfer or continued hosting after cancellation.

Security requirements belong in the scope: authentication, access rules, protection of data and deployment checks. Ask the team to explain the controls for your application. Do not infer a certification or security audit from the seven-day guarantee.

Role-based access can form part of your bespoke application. We need to understand who may view, change and approve each type of information, and test those boundaries before launch.

You can request confidentiality arrangements before sharing sensitive details. Keep your first enquiry high-level; do not include secrets, credentials or personal customer records. The team can agree a suitable way to exchange project information.

The SCS team receives contact-form enquiries through its project enquiry and email workflow. The privacy notice explains the form fields and purpose. Use the listed contact address for privacy questions or a deletion request.

No. Search runs against a local catalogue of reviewed answers. It does not send your question to a language model or sales inbox. Use the contact form separately when you want the team to receive an enquiry.

Yes, integrations are part of the bespoke offer. We first check the systems, available APIs, permissions and relevant data. External provider capabilities and access need verification before the start date.

A CRM connection can form part of the agreed application. Tell us which CRM you use and what should move between systems. We verify the available API and access before committing to the integration.

For work that touches existing systems, the team needs appropriate authorised access before the clock starts. Share credentials only through an agreed secure channel, never through this FAQ or a public URL.

Data migration can be included in the agreed scope. The team needs to review formats, volumes, access and validation requirements. Agree backups and rollback before moving production data.

Identify third-party access and approvals before agreeing the start. Ask the team to record dependency handling in the proposal. The FAQ does not invent an automatic extension or silently remove the delivery guarantee.

Yes. The seven-day commitment is to a deployed application, not simply source files. The proposal records the production environment, access and acceptance checks for your product.

The hosting arrangement depends on your requirements and the agreed operating service. Confirm provider, region, access, backups and cost in your proposal. This website does not assign one hosting arrangement to every application.

Domain setup can be part of the deployment scope. The team needs authorised DNS access and should agree ownership and renewal responsibility. External DNS and certificate dependencies need checking before launch.

Ask for backup frequency, retention, restore testing and recovery responsibilities in your operating agreement. Those details depend on the application; the FAQ does not publish an unsupported recovery-time promise.

The existing service tiers carry an agreed 99% monthly availability commitment for the service SCS controls, subject to access requirements and the exclusions in writing. If SCS breaches that commitment, there is no service fee for that month. Confirm your service terms before approval.

Maintain keeps the agreed application working under your operating agreement. Your proposal should define the included support and exclusions. It is different from an ongoing allowance for new product development.

Improve adds a scoped frontend change allowance to the operating service. Confirm the allowance and scope in the proposal; unused allowances do not roll over. It does not mean unlimited redesigns.

Evolve adds scoped full-stack changes to the operating service. The proposal defines that allowance, and unused allowances do not roll over. New work remains subject to an agreed scope.

We discuss the change with you and record its effect on scope, price and timing in writing before proceeding. New requirements need an agreed plan; they must not silently remove the protection attached to your original expectations.

Yes. Bespoke web applications and responsive platforms are part of the offer. The Work collection includes conference management, commerce and operational applications so you can inspect relevant examples.

Mobile-responsive platforms are part of the published capabilities. Specify required devices and workflows in the scope. Native app distribution and external app-store approvals need their own explicit deployment agreement.

Yes. The team builds workflow automation, reporting and integrations tailored to your processes. The requirements and acceptance checks define what runs automatically and what still needs a person to approve it.

AI integration is part of the offer where it suits your requirements. Agree data access, human review and failure handling. A model response is not proof that an external action completed successfully.

The software commitment must not be confused with hardware manufacturing or installation lead times. Connected systems projects need a separate plan for devices, procurement, field installation and external dependencies before the software start is agreed.

Open Work to browse applications, commerce and client websites. Filters separate studio products from client work; each case-study page links to its source project and describes what was built.

No. Atrium, Colloquium, Space and SpaceBrew are studio products. The portfolio labels known studio-owned products separately and does not present them as independent customer endorsements.

Do not infer that from the portfolio. The collection shows product and implementation examples; a seven-day delivery record needs dated evidence for that specific project. No historical delivery timing is invented.

The website includes attributed feedback from Hennie Schutte at Astra Construction, Corne Smit at Infinity Trading and Behanke Schutte at Blanco Bridal Couture. Their words are customer testimony, not a measured savings study.

SpaceCode Studios is run by a team of senior specialists. The studio is responsible for the agreed delivery and operating service. Use the project enquiry route to confirm who is accountable for your commission.

Use Tell us what you need to send your name, email and a short description of the software. Company and service category are optional. The team will help establish the scope; you do not need to arrive with a technical specification.

No. Describe what the product needs to do and who will use it. We work through the requirements, design direction and dependencies before agreeing the build. Do not send passwords or confidential datasets with your first enquiry.

The published commitment is a proposal within 48 hours of a complete scope. An initial enquiry may need clarification first. The team confirms expectations, the fixed development price and a start date before approval.

Yes. The contact form, sales email and listed WhatsApp contact are separate human enquiry routes. Nothing typed into this FAQ is silently forwarded to them. Choose Contact the team when you want to make that handoff.

Existing application work can be discussed with the team. Describe the change you need and the current platform; access, code quality and external dependencies need review before the scope and start can be agreed.

Atrium is SCS bespoke lifestyle orchestration for an active owner. It is commissioned around that person, their business and their standing decisions, rather than sold as a generic AI assistant.

Atrium works through the tools and channels agreed for the commission, retaining context and coordinating work. Specific integrations and permissions need to be agreed; do not assume access to every tool by default.

The people accountable for the commission set its role and permissions. Atrium begins supervised, and autonomy grows through demonstrated, verified work rather than automatic access to everything.

No. Research participation is optional and separate from a commercial enquiry. Use the Atrium page to discuss commissioning, or the research page if you want to contribute your perspective.

Try a shorter phrase or choose a topic. If the catalogue still has no suitable answer, use the separate contact page. We show a no-match state rather than inventing information.

No. It only retrieves reviewed information. Start dates, prices and refund decisions stay with the SCS team through a separate explicit enquiry. Search results cannot create a booking or change a contract.