Clear questions, clear answers.

If your process is a competitive edge — multi-brand F&B workflow, an unusual production flow, or a specific compensation rule — SaaS will force you to change the very way you win. For generic needs (email, basic accounting, file storage), use SaaS. For unique core operations, custom is cheaper in 3 years because you stop paying for constant workarounds.

A focused custom MVP typically runs USD 6k–25k for the first phase (3–4 months, one domain). SaaS subscriptions feel cheap upfront, but for 50+ users over 5 years, custom is often cheaper — with features that fit exactly. We help you do the honest total-cost-of-ownership math at kickoff.

Production-ready MVP: 8–14 weeks for one module. Subsequent features go much faster because the foundation exists. We don't promise 'launch in 2 weeks' — that's unrealistic. We also don't promise 'ready in a year' — that means we're not focused.

You do, fully — when the engagement is pure custom development. Source code is handed over, repo access full, documentation included. What stays with us: reusable components, internal libraries, and pre-existing Logixbase modules. Details locked in the contract, transparent.

Three options: (1) monthly retainer — we keep the wheel, (2) your internal team takes over with our docs + handover, or (3) hybrid — we're on call for big changes, your team handles the small ones. 24h SLA for critical bugs on the retainer.

Kickoff 1–2 weeks: map current workflow, identify jobs-to-be-done, define an MVP that ships in 12 weeks. Output: a scope doc with an estimate range, not a single number that will miss. We say no if your scope is infeasible within the budget — before the contract, not mid-build.

Yes. We've integrated with Accurate, Mekari Jurnal, Xendit, OY!, Midtrans, Moka POS, and several custom ERPs. For systems we haven't touched, we audit the API docs first — if there's an API, we integrate. If not, we discuss alternatives (export-import, RPA, or responsible scraping).

Scope always evolves, and we plan for it. We use two-week sprints with a review at the end of each. Small changes go into the backlog without a change order. Larger changes (effort >1 sprint) become a contract addendum with a new estimate. Fully transparent, with no surprise invoices.

That's exactly what we recommend. Phase 1 is always one shippable module — usually the most painful one today. Phase 2+ adds modules or deepens existing ones. Our philosophy: software in use and being refined > complete software that never ships.

Both available. Default: hosted by us in Singapore region (we handle deploy, uptime, backup). Want self-hosted (on-prem or your cloud)? We hand over full source code + infra docs. Decide at contract, not after launch.

Customization: we use Logixbase OMS or HRIS as the base, then add custom modules or fields for you — cheaper, faster, tied to Logixbase architecture. Custom development: built from scratch for your problem — more expensive, longer, free of constraints. For 70% of cases, customization is enough. We'll tell you honestly.

Our team imports from Excel, Google Sheets, Talenta, Mekari, Jubelio, Accurate, or custom databases — anything exportable. Dry-run on staging first, you validate samples, then we migrate production in your chosen window (usually weekend). Mismatches surface to you for decisions, not for us to guess.

Phase 1 (scoping + MVP): fixed price with an estimate range. Phase 2+: pick T&M (time and materials) if scope is still fluid, or a monthly retainer if you want a dedicated team. We don't push a specific model — we discuss what fits your budget and pace.

Default is us — infra on Neon + Vercel/Railway Singapore region, 24/7 monitoring, daily backups, 99.5% uptime target. If you want self-hosted, we hand over a full playbook. Enterprise: we can set up in your cloud account (AWS, GCP, Azure) and your team takes over post-handover.

Yes, and it is one of our most frequent engagements. We begin with a codebase and workflow audit (1–2 weeks, fixed price), producing a candid recommendation — continue, partial refactor, or rebuild. We have taken over an 8-month-stuck NodeJS project and shipped a clean version in 10 weeks. We have also advised a client that a rebuild would be cheaper than continuing — an assessment that proved correct.

Yes. Logixbase OMS is multi-warehouse native — stock per location, inter-warehouse transfers with documents, real-time visibility. For multi-country: each warehouse can have its own currency and tax rule. Fits brands with Jakarta-Surabaya warehouses, or expansions into Vietnam-Malaysia.

Yes. 'Brand' in OMS is separate from 'product' — one product can be listed under many brands with different prices, descriptions, and stock pools. Multi-brand operators (e.g. retail groups with 4 lines) can view consolidated or per-brand based on role.

For marketplace integration, we partner with middleware (Ginee, Jubelio, Forstok) or we build directly via official APIs. Two-way stock and order sync. Roadmap: native integration for Shopee and Tokopedia by late 2026, other marketplaces via middleware or custom build.

For Moka, Pawoon, and iREAP we integrate via API. For older POS systems (Olsera, MajooPos), we typically import daily sales files + sync stock manually. For F&B chains needing real-time POS-OMS sync, we build custom adapters — usually 4–6 weeks extra.

Three layers: (1) scheduled cycle counts — 5% of SKUs per week, system suggests which to check, (2) automatic gap analysis whenever a sale happens without stock decrement, (3) append-only audit log — every stock change tracked who, when, why. For >99% accuracy, your team's discipline matters too, not just software.

Yes. FIFO (First In First Out) default for general goods. FEFO (First Expiry First Out) for F&B and pharma — system picks nearest-expiry stock. Batch tracking for recall traceability — if a production batch has issues, you know immediately which customers received it.

Returns trigger an RMA document with structured reasons (defect, wrong item, customer cancel). Stock can go straight back to quarantine or restock based on condition. Refund links to the payment provider if integration exists (Xendit, Midtrans). Everything links back to the original order — you won't lose the trail.

Yes. Component-based templates — set header, logo, layout, tax lines, footer, T&Cs per brand. For very specific templates (custom field per region, multi-currency display, digital signatures), we build them during project setup or via custom development.

Yes. For multi-line orders with split stock, the system suggests split shipments with optimization (distance to customer, shipping cost, stock level). You accept the suggestion or override manually. Multiple tracking numbers, and the customer sees a consolidated status.

Tiers by orders per month + active SKUs + users. For Enterprise (>10k orders/mo or >50k SKUs), pricing is custom and discussed directly. We do not charge per-API-call or per-transaction — we consider that pricing model unfair to customers.

On clock-in, the app reads the device GPS and compares against the outlet radius set by admin (default 100m, configurable). Accuracy 5–15m in urban areas, 20–50m in low-signal areas. Anti-spoofing: we detect mock locations and selfie verification is a second layer. Bypass available for specific roles (field sales, managers).

One employee can clock in mornings at outlet A as a barista (rate A), take a break, then clock in afternoon at outlet B as a supervisor (rate B), all in one day. The system records each segment with its brand, location, role, and rate. Payroll auto-calculates the total. This capability is essential for multi-brand F&B operators.

Yes, this is a core HRIS Logixbase feature. Rate is set per (employee × brand × role) — not one rate per employee. Employee A can be USD 3/hr at brand X and USD 5/hr at brand Y, captured automatically from attendance segments, no manual input.

Indonesia: BPJS Ketenagakerjaan & Kesehatan, PPh 21 — we generate files in e-Filing and e-PPT formats. For SEA: SOCSO/EPF (Malaysia), VSS (Vietnam), SSS/PhilHealth (Philippines) — currently via custom export, native integration on 2026 roadmap. LATAM (IMSS Mexico, INSS Brazil) and Middle East (GOSI Saudi): custom export per requirement, buildable for Enterprise.

Yes, on the multi-country tier. Each entity can have its own OT rules, leave allotments, public holidays, and tax brackets. If you have teams in Jakarta and Ho Chi Minh, the system automatically applies the right country rules. We've run this for multi-country clients.

Yes. Employees request via the app, manager one-click approval, everything logged on the employee profile + reflected in payroll. Overtime auto-computed from attendance segments exceeding normal shifts. Annual leave tracking + pro-rate for new hires. Claims (transport, medical) with photo attachment + approval workflow.

Yes. Employment type is a field — you can set up permanent, contract, part-time, freelance, intern. Each type has different default rules (statutory benefits optional for freelance, OT caps for part-time, etc). Payroll output split per type for reporting.

Mobile app caches for offline clock-in/out — data syncs when signal returns. Selfie + geolocation captured locally. For chronically offline locations (remote warehouses), we provide kiosk mode on a tablet that syncs every 30 minutes. For laptops or desktops, offline is more limited — usually not the critical use case.

Configurable per role + per outlet. Barista role: mandatory. Manager role: optional. Flagship outlet: mandatory + face match against profile photo. Remote outlet: selfie only without face match (to save bandwidth). You configure.

Postgres on Neon, Singapore region. Access by role: employees see their own data, managers see their direct teams, HR sees all, owners see consolidated. Selfie photos stored in encrypted object storage, default 90-day retention (extendable per your policy). Audit log on every access to sensitive data.

This is actually the cleanest migration because your data is already tabular. Steps: (1) we audit your spreadsheet structure, (2) deduplicate + standardize format, (3) import to staging, (4) you validate samples, (5) cutover to production. Total: 1–3 weeks for operations with 5k–50k rows. Messy spreadsheets are not a problem — we work with them regularly.

Yes for all the above. We have import scripts for Talenta and Mekari (HRIS) and Jubelio and Accurate (OMS/Finance). For Zoho and other platforms, we use your CSV export + a custom import script (1–2 weeks). The trickiest part is usually not the data, but mapping concepts — in Talenta 'brand' isn't first-class, so mapping to Logixbase's multi-brand concept needs discussion.

Three strategies: (1) cutover outside business hours — typically Friday night or weekend, 2–6h downtime. (2) Run parallel 1–2 weeks — old and new systems run side by side, you use the new but the old is backup. (3) Phased migration — module by module, location by location. Pick by your risk tolerance.

Strongly recommended for critical migrations. During parallel (typically 2–4 weeks), you input into both systems and we compare output (reports, payroll) for validation. After 2 consistent payroll cycles, the old system is decommissioned. It takes longer and costs more, but carries far lower risk.

The old system isn't deleted — you retain access (or a snapshot) for at least 90 days post-cutover. If something serious arises in week one that we can't fix within 48h, you can revert. We also keep daily Logixbase backups for 30 days for minor rollbacks.

Growth tier and above: 2 live training sessions (admin + end-user), written docs, short video tutorials (3–5 min per feature), and 30-day support chat. Enterprise: on-site training 1–2 days, train-the-trainer for your team, dedicated CSM for the first 90 days. Employee adoption is the biggest success factor, and we take it seriously.

Yes. CSV or JSON export for every entity (employees, products, orders, transactions). For large exports (>100k rows), async job — we email a download link when ready. No vendor lock-in, no export fees.

You get a full export (CSV + JSON) for free within 30 days of cancellation. We keep data read-only for 90 days as a safety net. After 90 days, data is permanently deleted unless legal retention applies. Clear policy, no surprise.

Per-product subscription with tiers (Starter, Growth, Enterprise) based on users + volume. 14-day trial, no credit card. 15% discount on annual commitment. Custom development quoted separately (fixed price for phase 1, T&M or retainer after). No hidden fees, no predatory per-transaction charges.

Default: Neon Postgres Singapore region (SG). For clients needing data to stay in a specific country (Indonesian PDP Law, Singapore PDPA, Vietnam Cybersecurity Law, Brazil LGPD), we can deploy a tenant in the appropriate region on Enterprise — options: Indonesia (Jakarta), Vietnam (HCM), Brazil (São Paulo), UAE (Dubai). Specifics discussed at onboarding.

Currently SOC 2 Type II readiness (audit in progress, completion target 2026). Active controls: data encryption at rest + in transit, MFA mandatory for admins, append-only audit log, separation of duty in production, annual penetration test. For ISO 27001 and industry-specific (HIPAA, PCI-DSS), we have a roadmap but no current certification — if it's a hard requirement, we say so before contract.

UI languages: Indonesian, English, Vietnamese, Thai, Malay, Filipino, Spanish (Mexico), Portuguese (Brazil), Arabic — all in interface and documentation. Currencies: IDR, MYR, SGD, VND, THB, PHP, USD, MXN, BRL, AED, SAR, plus multi-currency reporting on Enterprise. Date, number, and name formats follow locale.

Core ops and support team in Indonesia (Jakarta). We serve clients in Indonesia, Singapore, Malaysia, Vietnam, Thailand, Philippines, Mexico, Brazil, UAE, and Saudi Arabia — remote onboarding, localized docs, payroll output in country-correct formats. On-site implementation outside Indonesia is typically quarterly visits on Enterprise.

Chat & email support: 09:00–21:00 WIB (UTC+7), 7 days a week. Response: 4 business hours for all tiers, 1 hour for Enterprise. Critical issues (system down, payroll deadline): 24/7 hotline on Enterprise with a 30-minute response SLA. Responses come from real support staff, not bots, in the same language you wrote in.

Yes, on Enterprise. Options: (1) full on-premise on your servers — we install + hand over an ops playbook, (2) private cloud in your AWS/GCP/Azure account — we set up + manage or hand over, (3) Logixbase dedicated tenant in your chosen region. Setup + license cost varies. Onboarding 4–8 weeks depending on complexity.